Bug 2307237 - Using pigz with podman pull causes CRC error
Summary: Using pigz with podman pull causes CRC error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: zlib-ng
Version: 40
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Tulio Magno Quites Machado Filho
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-08-22 09:43 UTC by Jonas Jonsson
Modified: 2024-09-19 00:17 UTC (History)
17 users (show)

Fixed In Version: zlib-ng-2.1.7-3.fc42 zlib-ng-2.1.7-2.fc40
Clone Of:
Environment:
Last Closed: 2024-09-12 16:50:56 UTC
Type: Bug
Embargoed:
tuliom: needinfo-


Attachments (Terms of Use)

Description Jonas Jonsson 2024-08-22 09:43:49 UTC
Description of problem:
Trying to pull a container image from docker hub but get crc32 mismatch.
Replacing /usr/bin/pigz with a symlink to /usr/bin/gzip solves the issue.

Not sure if this should be considered podman or pigz issue.

Version-Release number of selected component (if applicable):
pigz-2.8-4.fc40.x86_64
gzip-1.13-1.fc40.x86_64
podman-5.2.1-1.fc40.x86_64


How reproducible:
Everytime

Steps to Reproduce:
1. docker pull espressif/idf:v5.3
2.
3.

Actual results:
$ docker pull espressif/idf:v5.3
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Resolved "espressif/idf" as an alias (/home/jonas/.cache/containers/short-name-aliases.conf)
Trying to pull docker.io/espressif/idf:v5.3...
Getting image source signatures
Copying blob 12ca5ee7db2a done   | 
Copying blob 9e694093934d skipped: already exists  
Copying blob 91cde73b5485 skipped: already exists  
Copying blob 74b4516c4840 skipped: already exists  
Copying blob dbd7e158b841 done   | 
Copying blob 3713021b0277 skipped: already exists  
Copying blob e7e4560058ce done   | 
Error: copying system image from manifest list: writing blob: storing blob to file "/var/tmp/container_images_storage2216285505/2": pigz: skipping: <stdin>: corrupted -- crc32 mismatch: exit status 1
$

Expected results:
Working pull.

Additional info:

Comment 1 Lokesh Mandvekar 2024-08-22 14:07:30 UTC
Hi Jonas, could you please file an issue with upstream podman on github https://github.com/containers/podman/issues/new/choose ? Upstream is more active on github than over here, and this might include changes in github.com/containers/storage library too.

Comment 2 Giuseppe Scrivano 2024-09-03 19:45:12 UTC
it is an issue in zlib-ng.  Filed an issue upstream: https://github.com/zlib-ng/zlib-ng/issues/1772

Comment 3 Tulio Magno Quites Machado Filho 2024-09-04 13:03:46 UTC
@gscrivan , could you provide the output from 'rpm -qa | grep zlib-ng', please?

I see you were able to reproduce this issue with commit ID e4fb3803afb8b46131abdeaaf927575d06621b0a, but I'd like to confirm which zlib-ng version is affected on Fedora too.

Comment 4 Tulio Magno Quites Machado Filho 2024-09-04 13:26:36 UTC
I managed to reproduce the issue with instructions from https://github.com/madler/pigz/issues/123

This is the package I used:
zlib-ng-compat-2.1.7-1.fc40.x86_64

Comment 5 Tulio Magno Quites Machado Filho 2024-09-10 19:16:50 UTC
I've just created a PR for rawhide here: https://src.fedoraproject.org/rpms/zlib-ng/pull-request/23

I have scratch builds available:
- rawhide: https://koji.fedoraproject.org/koji/taskinfo?taskID=123213813
- f40: https://koji.fedoraproject.org/koji/taskinfo?taskID=123214531

@gscrivan , could you check if it fixes the issue for you, please?

I'm preparing a PR for f40 too.

Comment 6 Giuseppe Scrivano 2024-09-10 19:42:50 UTC
thanks.  It solves the problem for me.

There is also an upstream patch that solves the error: https://github.com/zlib-ng/zlib-ng/pull/1773

Comment 7 Tulio Magno Quites Machado Filho 2024-09-10 20:48:17 UTC
I applied the patch from that PR.
Thanks!

Comment 8 Fedora Update System 2024-09-11 14:39:21 UTC
FEDORA-2024-fc28e4ebac (zlib-ng-2.1.7-3.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-fc28e4ebac

Comment 9 Fedora Update System 2024-09-11 19:35:58 UTC
FEDORA-2024-e5dd8c3908 (zlib-ng-2.1.7-3.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-e5dd8c3908

Comment 10 Fedora Update System 2024-09-12 02:20:33 UTC
FEDORA-2024-e5dd8c3908 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-e5dd8c3908`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-e5dd8c3908

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2024-09-12 16:50:56 UTC
FEDORA-2024-fc28e4ebac (zlib-ng-2.1.7-3.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2024-09-12 18:36:09 UTC
FEDORA-2024-b25a4bcbb7 (zlib-ng-2.1.7-2.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-b25a4bcbb7

Comment 13 Fedora Update System 2024-09-13 02:42:00 UTC
FEDORA-2024-b25a4bcbb7 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-b25a4bcbb7`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-b25a4bcbb7

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 14 Fedora Update System 2024-09-14 02:00:50 UTC
FEDORA-2024-b25a4bcbb7 (zlib-ng-2.1.7-2.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2024-09-19 00:17:39 UTC
FEDORA-2024-e5dd8c3908 (zlib-ng-2.1.7-3.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.