Closed ChrisMcKee closed 1 year ago
Hey Chris, we made a lot of improvements in Windows containers to reduce their size. You can read about it in our blog for months Jan 2023, Feb 2023, and May 2023. We pruned almost everything that was not required to be present in the container image. Is there anything specific you wanted to point us to?
https://devblogs.microsoft.com/dotnet/we-made-windows-server-core-container-images-40-smaller/ the uncompressed container sizes when this post was written was around 2gig with FX.
I was trying to work out how that work seemingly vanished into the ether leaving us pulling 5+ gig images from the msft container repo (which for added pleasure seems to cap connections at 6mbps)
Hard to workout how to improve this from the outside as none of the construction is public; Vs the options when creating amis/VMware images.
Is your feature request related to a problem? Please describe. There was a great post a couple of years back ...
Shrinking the windows images down; but soon after an update was released for windows and the bloat returned never to be reduced again.
Describe the solution you'd like We have no way to debloat a windows container; you can't use docker-slim against windows containers or squash to reduce the layers and you can't export the image to tar to remove things that have no real place in a container used to wrap a dotnet application.
Either tooling or produce a base image with little to none of the stuff installed / pre-cached; and layer on the features; i.e. There's updates installed for tablet pc path and handwriting, text to speech etc which seems off.
Additional context