When running podman run --rm -it sonarqube:latest I found (to my surprise) it exists in four different registries.
podman run --rm -it sonarqube:latest
? Please select an image: ▸ registry.fedoraproject.org/sonarqube:latest registry.access.redhat.com/sonarqube:latest registry.centos.org/sonarqube:latest docker.io/library/sonarqube:latest
But when selecting any of the three first, it fails with an error message
✔ registry.fedoraproject.org/sonarqube:latest Trying to pull registry.fedoraproject.org/sonarqube:latest... manifest unknown: manifest unknown Error: Error initializing source docker://registry.fedoraproject.org/sonarqube:latest: Error reading manifest latest in registry.fedoraproject.org/sonarqube: manifest unknown: manifest unknown
I'm not familiar with the structure of container registries, but in terms of dnf repositiries it would seem to me the metadata doesn't match the actual contents.
if you are using unqualified image names, podman will ask you from which registry you want to pull. It doesn't actually query those registries at this point. In a non-interactive terminal, It will try each registry on this list (which is defined in /etc/containers/registries.conf) until one is found. If you want to know exactly on which registry the image can be found, you can use podman search. The recommend way is to always use fully qualified image names when possible.
/etc/containers/registries.conf
podman search
As the previous comment explained this is not a registry issue.
Issue status updated to: Open (was: Closed)
Metadata Update from @smooge: - Issue close_status updated to: Invalid - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue status updated to: Closed (was: Open) - Issue tagged with: low-gain, low-trouble, ops
Metadata Update from @smooge: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Thanks for the information and sorry for spamming. I had used short names previously, but it turns out the ones I had tried were all aliases in the shortnames.conf file. I didn't realise I was using that feature, and was surprised when I suddenly saw a different behavior.
shortnames.conf
Again, thanks, and sorry.
Log in to comment on this ticket.