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

Split dockerBase between builder and final stages so that final images can be slimmed down. #173

Closed
ewilkins-csi opened this issue Jul 9, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@ewilkins-csi
Copy link
Contributor

Right now, both the image used to bundle the virtual environment during containerize-dependencies is exactly the same as the image used as the final packaging/runtime image. Because dev tools like gcc are often required during the build but not at runtime, final images can be much smaller if we allow building the virtual env with a more "full" base image and use a slimmed down version of that base image for the final image.

This does introduce some complexity for users as they will need to ensure that the value set for the builder stage is compatible with the value set for the final stage, but the old functionality can easily be used by simply providing the same value for both.

@ewilkins-csi ewilkins-csi self-assigned this Jul 9, 2024
@ewilkins-csi ewilkins-csi added this to the 2.16.1 milestone Jul 9, 2024
@ewilkins-csi ewilkins-csi added the enhancement New feature or request label Jul 9, 2024
ewilkins-csi added a commit that referenced this issue Jul 9, 2024
…-img

#173 add support for a separate final image in containerize-dependencies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant