Bug 2058491
| Summary: | podman 3.0.1 ~ 3.2.3: docker-archive doesn't support modifying existing images | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | XinhuaLi <xili> |
| Component: | podman | Assignee: | Valentin Rothberg <vrothber> |
| Status: | CLOSED WONTFIX | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.4 | CC: | bbaude, dwalsh, jligon, jnovy, lsm5, mheon, pthomas, tsweeney, umohnani, vrothber |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-09-13 14:16:33 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
XinhuaLi
2022-02-25 06:26:52 UTC
Thank you for reaching out.
> We cannot see the issue against "podman version 3.4.2", Please help to check. Will we backport the fix to RHEL 8.4 EUS?
The docker-archive has never supported writing to an existing archive. Can you recheck whether 3.4.2 really works in your tests? I just tried and it does not.
Note that `podman save` supports writing multiple images at once to a docker-archive since version v2.1.0. For instance, via `podman save fedora centos ubi-8 -o multi-archive.tar`.
Hi Valentin, Good day. Please check logs below ------------------------------------------------ # podman save -o rhceph-5-rhel8_latest.tar 9e20ad683d05 Copying blob a9820c2af00a done Copying blob 3d5ecee9360e done Copying blob 2f47f818417e done Copying config 9e20ad683d done Writing manifest to image destination Storing signatures # podman -v podman version 3.4.2 ------------------------------------------------ Regards Sam (In reply to XinhuaLi from comment #2) > [...] > # podman save -o rhceph-5-rhel8_latest.tar 9e20ad683d05 > Copying blob a9820c2af00a done > Copying blob 3d5ecee9360e done > Copying blob 2f47f818417e done > Copying config 9e20ad683d done > Writing manifest to image destination > Storing signatures Did the file `rhceph-5-rhel8_latest.tar` exist *before* running `podman save`? Hi Valentin, Good day. Please refer to the quick test below ------------------------------------------------------------------ # podman -v podman version 3.2.3 # ls rhceph-5-rhel8_latest.tar ls: cannot access 'rhceph-5-rhel8_latest.tar': No such file or directory # podman save -o rhceph-5-rhel8_latest.tar 9e20ad683d05 Getting image source signatures Checking if image destination supports signatures Error: Can not copy signatures to docker-archive:rhceph-5-rhel8_latest.tar: Storing signatures for docker tar files is not supported ------------------------------------------------------------------ Regards Sam (In reply to XinhuaLi from comment #4) > [...] > # podman save -o rhceph-5-rhel8_latest.tar 9e20ad683d05 > Getting image source signatures > Checking if image destination supports signatures > Error: Can not copy signatures to docker-archive:rhceph-5-rhel8_latest.tar: > Storing signatures for docker tar files is not supported > ------------------------------------------------------------------ That is a different error compared to the one listed in the initial report: > Error: unable to save "9e20ad683d05": error copying image to the remote destination: Error initializing destination docker-archive:rhceph-5-rhel8_latest.tar: docker-archive doesn't support modifying existing images Can you try again saving an image (without signatures)? The associated case has been closed and we can close the bug too. |