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
Building/running gcr:deploy uses up 20GB #73
Comments
Unfortunately unless we start using minimal distro instead of ubuntu we cannot reduce to much the size of the image... |
...do we have to use docker? |
We can switch to the docker_push that @mattmoor had come with but for pull we are still depending on using apt-get install which requires docker. Ideally we would switch to use a dockerless version of it which would save several giga. |
The three images we are building with docker are:
(see https://github.com/bazelbuild/continuous-integration/tree/master/base) I am pretty sure we can make it back to have dockerless images, @mattmoor have probably more visibility about the existing images we can reuse (Java / Jekyll / SSH / g++ / python / python3 / go) |
So we only build 2 images now. Closing this one as we cannot do much more than switching to distroless in that respect. |
@damienmg You can still share the base portion of those images so you aren't paying for multiple copies. e.g. put this in one Dockerfile:
Tag it "base", then make the others:
Right now each of these images will produce redundant versions of these layers. |
This is impractical.
(Disk usage of /, the red area is docker.)
The text was updated successfully, but these errors were encountered: