Skip to content
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

Potentially corrupt blob #19

Open
com6056 opened this issue Dec 16, 2023 · 3 comments
Open

Potentially corrupt blob #19

com6056 opened this issue Dec 16, 2023 · 3 comments

Comments

@com6056
Copy link
Contributor

com6056 commented Dec 16, 2023

Haven't narrowed it down yet, but ran into this pull error which went away when I cleared our the S3 bucket:

  Warning  Failed                  3s                     kubelet                  Failed to pull image "docker.io/foo/bar@sha256:f05918ce7a92b84415e1abaa1c6ba0d7212b05adca41360673873bc85be88b91": rpc error: code = Unknown desc = writing blob: storing blob to file "/var/tmp/storage2866776745/3": happened during read: unexpected EOF

Same deal when trying to pull directly from the node too:

[root@node ~]# crictl pull docker.io/foo/bar@sha256:f05918ce7a92b84415e1abaa1c6ba0d7212b05adca41360673873bc85be88b91
E1216 00:47:48.098893    6802 remote_image.go:171] "PullImage from image service failed" err="rpc error: code = Unknown desc = writing blob: storing blob to file \"/var/tmp/storage4078425335/7\": happened during read: unexpected EOF" image="docker.io/foo/bar@sha256:f05918ce7a92b84415e1abaa1c6ba0d7212b05adca41360673873bc85be88b91"
FATA[0005] pulling image: rpc error: code = Unknown desc = writing blob: storing blob to file "/var/tmp/storage4078425335/7": happened during read: unexpected EOF

I'm guessing the blob being pulled somehow got into a funky state in the bucket since the issue went away after I cleared out the S3 bucket, need to dig in more but wanted to put this into an issue in case anyone knew what might have happened. Thanks!

@com6056 com6056 changed the title Corrupt manifest and/or blob Potentially corrupt manifest and/or blob Dec 16, 2023
@com6056 com6056 changed the title Potentially corrupt manifest and/or blob Potentially corrupt blob Dec 16, 2023
@mcronce
Copy link
Owner

mcronce commented Mar 20, 2024

This is, hopefully, fixed by the digest checking added in v0.4.4

@thejosephstevens
Copy link

We'd be happy to test this out! We see this issue fairly frequently across our systems, so we should be able to validate if it's gone. We're upgrading from 0.3.8, is there anything we should be aware of while upgrading? I don't see upgrade notes anywhere, not sure if I'm looking in the right place

@mcronce
Copy link
Owner

mcronce commented Apr 23, 2024

@thejosephstevens you shouldn't need to do anything special, the only reason I bumped from v0.3 to v0.4 is because of an additional feature added to URL parsing to support CRI-O. I'm uploading v0.4.5 now to fix an issue with enabling this digest checking feature in the helm chart.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants