-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
podman cannot pull certain images from docker hub #23822
Comments
@giuseppe PTAL There is also a fedora bz reporting the same thing with a different image, https://bugzilla.redhat.com/show_bug.cgi?id=2307237 |
Facing the same with Users on the Docker side have said it's something to do with containerd preferring unpigz for extraction when it's installed, and removing the pigz package resolves this. Edit: |
It was added in containers/storage#1964 with podman 5.2 to make it faster. I however can pull the mention images fine though so it is not a consistent error either. |
Will try and gather some additional information.
|
What is your pull speed? It may be very well related to the buffer/read size. |
Yeah I think slower is better, I have a 7 MiB/s and it pulls fine |
I am able to reproduce locally. @Luap99 could you try against a local registry? I've used the following commands:
|
@giuseppe Sure local registry seem to work fine for me as well. I used I am still on f39 in case it matters and use podman from main right now, pigz is |
it seems to be a pigz issue:
|
opened an issue for pigz: madler/pigz#123 |
Also seeing the same with
Exact same error:
|
Given that this might be a bigger issue you can work around this issue on fedora as user with
Which will un-parallel pigz back to regular gzip, which works flawlessly. Once a fix is out you can |
For users on |
There are a number of jobs that are failing to pull images due to corruption and a crc32mismatch[1] There is an open issue for this problem in the podman repo[2] that suggests this change as a workaround. This workaround should be removed when the related issues are resolved. [1] https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/12677/pull-kubevirt-e2e-k8s-1.31-sig-compute/1833657514537783296#1:build-log.txt%3A262 [2] containers/podman#23822 [3] zlib-ng/zlib-ng#1772 Signed-off-by: Brian Carey <[email protected]>
There are a number of jobs that are failing to pull images due to corruption and a crc32mismatch[1] There is an open issue for this problem in the podman repo[2] that suggests this change as a workaround. This workaround should be removed when the related issues are resolved. [1] https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/12677/pull-kubevirt-e2e-k8s-1.31-sig-compute/1833657514537783296#1:build-log.txt%3A262 [2] containers/podman#23822 [3] zlib-ng/zlib-ng#1772 Signed-off-by: Brian Carey <[email protected]>
the issue was fixed upstream in zlib-ng zlib-ng/zlib-ng#1773 So closing as there is nothing more to do on our side |
FYI - today's rounds of updates in Silverblue 40 brought |
Issue Description
podman pull docker.io/ollama/ollama:rocm fails consistently with
Error: writing blob: storing blob to file "/var/tmp/container_images_storage791753323/1": pigz: skipping: <stdin>: corrupted -- crc32 mismatch: exit status 1
All :rocm tags from the image are affected going back as far as i can tell.
The :latest (smaller, dont contain the 4GB rocm binary layer) images are not affected.
skopeo is affected with the same issue.
Workaround: loading the image with
docker pull
works, and exporting it to a .tar, and importing it with podman image load works.Steps to reproduce the issue
Steps to reproduce the issue
podman pull docker.io/ollama/ollama:0.3.8-rocm
Describe the results you received
Error: writing blob: storing blob to file "/var/tmp/container_images_storage791753323/1": pigz: skipping: <stdin>: corrupted -- crc32 mismatch: exit status 1
Describe the results you expected
podman pull
should successfully pull the image, likedocker pull
canpodman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: