-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Use --squash
for images
#3334
Comments
This would possibly double or more the storage requirements on our build servers and prevent users from being able to share layers between image updates and across versions thus increasing their storage needs as well. It will also make it even harder to clean up old images, since we would have to track the non-squashed version of each image along with its flat version. You may be interested in the progress of moby/moby#34423 which will hopefully make multi-line No issue that I recall tracking multi-stage builds in official-images. |
Added #3383 to track multi-stage builds ;) |
Also it looks like |
Agreed, good call 👍 In either case, we'll definitely not be using squash here; will leave discussion of multi-stage to that new issue. |
Multi-stage is definitely better that squash. My thought was that one is available now, one is not 🙂
Could you link to some issue tracking that (if it exists)? |
Would it be possible to start using
--squash
when building the official images? I'd love to be able to drop all the&& \
in the node docker files, and stop worrying so much about layers and just caring about cleaning up.https://docs.docker.com/engine/reference/commandline/build/#squash-an-images-layers-squash-experimental-only
(semi-related, is there an issue I can track for when we can start to use multi-stage builds?)
The text was updated successfully, but these errors were encountered: