You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
Activity
macsux commentedon 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 commentedon 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.
ivanovac commentedon Jan 26, 2026
I'm closing this as no activity to this issue recently. If it is still applicable, please reopen.
obligaron commentedon Jan 26, 2026
This still happens and costs time and resources.
Note: something similar happens only when installing the .net runtime (this happens multiple times)
Edit: I can't reopen the issue.
ivanovac commentedon Jan 30, 2026
Reopened as @obligaron pointed out that this issue is still relevant