-
Notifications
You must be signed in to change notification settings - Fork 422
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
minimize image contents #695
Comments
Doing this has the benefit of:
It has the downside of:
IMHO those are typically a preferable trade-off, it's hard to predict layer sharing anyhow and the total image size should shrink. The builds seem relatively maintainable. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
Done! Cut by about half. |
Hmm, seems to not work on cross-platform builds. |
It looks like I just needed to reinit buildx, which is actually in our Makefile. Not sure how to ensure that is fresh, but I am building the v4.0.0-rc1 for all platforms now. |
We have a pattern developed for kube-proxy from the kind haproxy image based on the ideas in bazel rules_docker where you copy over a subset of additional debian package contents to a distroless image resulting in an image with all the binaries + libraries you need AND their package info / license but nothing else.
See:
https://github.com/kubernetes-sigs/kind/tree/main/images/haproxy
https://github.com/kubernetes/release/tree/master/images/build/distroless-iptables/distroless
Semi-related: #518 (though it appears we're still going to need a shell)
Seems like git-sync would be a good use case for this approach.
The text was updated successfully, but these errors were encountered: