Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid installing SDK on container #591

Open
Tandis5 opened this issue Jun 10, 2022 · 2 comments
Open

Avoid installing SDK on container #591

Tandis5 opened this issue Jun 10, 2022 · 2 comments

Comments

@Tandis5
Copy link

Tandis5 commented Jun 10, 2022

With the upgrade to .NET 6, the SDK installation is taking up a lot more space. We are having to add space to our containers, and that is space that really isn't needed. Would it be possible to get a buildpack that only installs the runtime and not the SDK? We always deploy the published app so we don't need the SDK taking up space.

@macsux
Copy link

macsux commented Jun 14, 2022

If this issue is tackled, I recommend this be an option rather than the default behavior. There are existing demos that rely on the presence of SDK in a container to work properly.

I recommend exposing a way to instruct buildpack to compile for self-contained mode. This way only assemblies used by the app will be included further reducing size. This way the container doesn't need to have dotnet dependency at all.

@Tandis5
Copy link
Author

Tandis5 commented Jun 14, 2022

Just to be clear... our apps are not being built self-contained. And they aren't being built at all by the buildpack. Our apps are built/published prior to being pushed to PCF. We just need the .NET runtime to run them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Not scoped
Development

No branches or pull requests

3 participants