-
-
Notifications
You must be signed in to change notification settings - Fork 152
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
oci_image uses significantly more disk space than container_image from rules_docker #439
Comments
I think this is fixed by that #440 - @SanjayVas if you have time, could you patch that in and verify? |
@alexeagle partially. we still copy blobs from base image (copy_to_directory) into oci_image's oci-layout (treeartifact) which causes duplication of the blobs. |
but that's a bigger fix and i don't have time to contribute. happy to review if somebody else is willing to contribute it. |
rules_oci outputs additional layer blobs that result in the Bazel cache being too large. See bazel-contrib/rules_oci#439
Sorry, the migration to rules_oci was prefactoring for migrating our tree of repos to Bzlmod. I can possibly try after that is done, but it will of course be easier if a version with that change has been published to BCR. |
rules_oci outputs additional layer blobs that result in the Bazel cache being too large. See bazel-contrib/rules_oci#439
oci_image
appears to copy all base image layer blobs to its Bazel output tree. Additionally it temporarily takes up even more space due to running a separate registry for each target.I believe
container_image
fromrules_docker
only has the created layer(s) in its output.Anecdotally, this blew up my CI. My compressed Bazel output cache went from ~3 GiB to ~20 GiB when migrating from rules_docker to rules_oci.
The text was updated successfully, but these errors were encountered: