You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
is impossible: 8e75cbc5b25c may have many different names, including nginx@sha256:$multiArchDigest and nginx@sha256:perArchDigest and nginx@sha256:$recompressedDifferentDigest. When inspecting by ID, the Digest field only reports one value, and it fundamentally can’t match 2/3 or more.
The caller’s assumptions must be revisited.
Now, the digest tracking in Podman is known to be problematic, but fixing that would not affect the design issue above.
Issue Description
The digest of an image used to be consistent when queried from a repository but for some (at least) multi-arch images this is no longer the case.
however
So by id or by name are different and in particular do not match unique Digest in the repository:
So the unique digest is inconsistent from the choice of Digests.
Steps to reproduce the issue
Steps to reproduce the issue
$ skopeo inspect docker://docker.io/nginx:1.23-alpine | jq .Digest
podman pull docker://docker.io/nginx:1.23-alpine
podman image list
podman image inspect docker.io/library/nginx:1.23-alpine | jq .[].Digest
podman image inspect 8e75cbc5b25c | jq .[].Digest
The two digest from the last commands do not match.
Describe the results you received
Describe the results you received
digests do not match.
Describe the results you expected
Describe the results you expected
podman image inspect docker.io/library/nginx:1.23-alpine | jq .[].Digest
podman image inspect 8e75cbc5b25c | jq .[].Digest
skopeo inspect docker://docker.io/nginx:1.23-alpine | jq .Digest
should produce a consistent Digest after an image is pulled.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
This is latest release in Fedora rawhide.
Same change in behaviour also occurred between podman 4 and podman 5 with RHEL 9.4->9.5.
https://issues.redhat.com/browse/RHEL-68539
Additional information
Probably only with multi-arch images.
The text was updated successfully, but these errors were encountered: