-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
What would it take to add "apk" extraction to docker_build
#30
Comments
@dlorenc FYI |
For java specifically, here's another example of installing a JRE without a package manager, and stripping out lots of parts: |
I don't think APKs and debs will mix and match very well due to the glibc/musl difference, but it might still be worth exploring. |
Yeah, I have started to introduce the nuance of "minimal" vs. "small" in my talking points. Ultimately, if we have users with the requirement "small at all costs", who aren't concerned about compatibility with glibc, then this route might be an appealing alternative to glibc and debs, but it would require a completely new image stack. I wonder if in the limit Bazel's cross compilation story will be what we want to key off of here. |
Closing old bugs |
In the pursuit of tiny images,
udeb
came up, but wasn't sufficient for the JRE.We should consider whether simply using APK provides smaller footprints.
Here's where
pkg_tar
is extracting the deb's data: https://github.com/bazelbuild/bazel/blob/master/tools/build_defs/pkg/build_tar.py#L147The text was updated successfully, but these errors were encountered: