Podman issue pulling from local registry

Latest response

Running RHEL 8.1 with Podman 1.4.2-stable2. I've used Docker CE before, however learning Podman. We are running a local Registry with Quay.

I'm able to log into Quay via command line.

I'm running everything as rootless.

When I try to pull a redhat-ubi image from the local registry, this is the error message that I get:

[cmiller@foo ~]$ podman pull server.url.here:portnumber/foo-software/redhat-ubi
Trying to pull server.url.here:portnumber/foo-software/redhat-ubi...ERRO[0000] Error pulling image ref //server.url.here:portnumber/foo-software/redhat-ubi:latest: Error initializing source docker://server.url.here:portnumber/foo-software/redhat-ubi:latest: Error reading manifest latest in server.url.here:portnumber/foo-software/redhat-ubi: manifest unknown: manifest unknown 
Failed
Error: error pulling image "server.url.here:portnumber/foo-software/redhat-ubi": unable to pull server.url.here:portnumber/foo-software/redhat-ubi: unable to pull image: Error initializing source docker://server.url.here:portnumber/foo-software/redhat-ubi:latest: Error reading manifest latest in server.url.here:portnumber/foo-software/redhat-ubi: manifest unknown: manifest unknown
[cmiller@foo ~]$

I've added the local registry to /etc/containers/registry.conf and added it first:

[registries.search]
registries = ['server.url.here:portnumber', 'registry.redhat.io', 'registry.access.redhat.com', 'quay.io', 'docker.io']

I find it odd Podman is trying to initializing source of docker, when I'm using the local registry of Quay.

CM
Log in to join the conversation

Responses

DD Red Hat Community Member 35 points
13 April 2021 1:28 PM

The docker:// in the error is not referring to a host, but the transport/protocol. It is simply using the docker registry compatible protocols to pull the image, so that should be fine. That error is typical of a missing image or one with incomplete/wrong metadata in the registry. Are you able to pull this image with docker? What happens if you add a tag, such as podman pull server.url.here:portnumber/foo-software/redhat-ubi:latest?

DD Red Hat Community Member 35 points
13 April 2021 1:29 PM

Also, can you run podman with '--log-level debug' and post the full output?

CM Active Contributor 226 points
13 April 2021 2:48 PM

It was a simple mistake. Quay is our Registry, and it seems like it needs a tag in order to pull successfully. That tag has to be setup as well, in order for a successful pull. Can't just pull a container like in Docker and without specifying the lastest tag, you get the latest images file (I'm coming from a Docker CE/EE background).

thanks