On systems where the default registries are configured under /etc/containers, podman-hpc pull on an image without registry url prefix will try to use the configured default registries. However, the last step of the process doing the migration of the image will fail.
The migration is done by taking the same image name without the registry prefix, which results in "image not found" error.
An example of the issue is
~> podman-hpc pull opensuse/leap:15.5
Resolved "opensuse/leap" as an alias (/etc/containers/registries.conf.d/000-shortnames.conf)
Trying to pull registry.opensuse.org/opensuse/leap:15.5...
Getting image source signatures
Copying blob b521da086976 done |
Copying config d3642ef487 done |
Writing manifest to image destination
d3642ef48786e0a2709a0189840e3c5b67faf943b5aded34ea587d1514fb4745
INFO: Migrating image to /pscratch/sd/-----/storage
ERROR:root:Image opensuse/leap:15.5 not found
The migration works if doing podman-hpc migrate d3642ef48786e0a2709a0189840e3c5b67faf943b5aded34ea587d1514fb4745.
A suggested fix is to use the hash of the image (as printed right before the line INFO: Migrating image to ) when doing the automated migration.
On systems where the default registries are configured under
/etc/containers,podman-hpc pullon an image without registry url prefix will try to use the configured default registries. However, the last step of the process doing the migration of the image will fail.The migration is done by taking the same image name without the registry prefix, which results in "image not found" error.
An example of the issue is
The migration works if doing
podman-hpc migrate d3642ef48786e0a2709a0189840e3c5b67faf943b5aded34ea587d1514fb4745.A suggested fix is to use the hash of the image (as printed right before the line
INFO: Migrating image to) when doing the automated migration.