-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-10.0
-
None
-
No
-
Low
-
rhel-image-mode
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
There are differences in the tags for the image rhel10/rhel-bootc between the ones listed in Red Hat catalog and the actual registry.
For example, "rhel10/rhel-bootc" image in the catalog has a tag "10.0-1756357951" but this is not pullable,
[quickcluster@node-0 ~]$ podman pull registry.redhat.io/rhel10/rhel-bootc:10.0-1756357951
Trying to pull registry.redhat.io/rhel10/rhel-bootc:10.0-1756357951...
Error: initializing source docker://registry.redhat.io/rhel10/rhel-bootc:10.0-1756357951: reading manifest 10.0-1756357951 in registry.redhat.io/rhel10/rhel-bootc: manifest unknown
However, when the last digit of the tag is changed from "1" to "0" (10.0-1756357950), the image is pulled,
[quickcluster@node-0 ~]$ podman pull registry.redhat.io/rhel10/rhel-bootc:10.0-1756357950
Trying to pull registry.redhat.io/rhel10/rhel-bootc:10.0-1756357950...
Getting image source signatures
Checking if image destination supports signatures
Copying blob 615f29149dfa done |
Copying blob 615f29149dfa done |
Copying blob 615f29149dfa done |
Copying blob f25308b2e280 done |
.
.
.
Copying config 28ac515fec done |
Writing manifest to image destination
Storing signatures
28ac515fec5052b472f5648d462de8eb9e29dd9e283a1eda49458e1edf0bfeff
