-
Notifications
You must be signed in to change notification settings - Fork 788
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
writing blob: Size mismatch #2437
Comments
Same thing with |
This doesn't seem to be specific to |
The manifest contains
The old (currently used) testimage 20240123 does not so I assume this might have something to do with zstd compression |
Notes:
|
… and that size seems to come from adding the size of file contents ( |
I think I know how to fix this, working on it now. If that hypothesis is correct, this means that re-pushes of zstd:chunked layers have been broken for about 1.5 years — i.e. we have a testing gap. |
We have many zstd testing gaps. We've never actually done any real testing anywhere in CI, only very-halfhearted efforts. I wonder if this is the bug that keeps blocking my buildah parallel tests PR? |
containers/storage#2130 might be a fix (absolutely untested!) to unblock, we should have a better one. Do we have a generic: "push an image (using our default settings); pull it (without reusing any layers); push it again" test? That’s essentially what broke here. |
Confirmed that (an updated version of) containers/storage#2130 fixes this, the metadata now contains the correct size. |
A friendly reminder that this issue had no activity for 30 days. |
This works correctly with |
Possibly a broken image or manifest? And possibly because I ^Ced the first time I pushed it, then rebuilt it and pushed a completely different one? Anyhow I don't know the root cause nor how to investigate further nor even where to report this or if it's even a bug.
skopeo copy docker://quay.io/libpod/testimage:20241009
works just fine.The text was updated successfully, but these errors were encountered: