Introduction
This is another article about how to solve an error message upon executing a podman command. The main purpose is to pull an image from a certain image repository. Furthermore, this article is actually has a connection with another article with the title of ‘How to Solve Error Message manifest unknown: manifest unknown when executing podman to pull image’ in this link. Basically, between the article, the error appears at the same time. It appears on the process for pulling the image is using the ‘podman’ command or ‘podman’ tool. The execution of pulling the image exist as follows :
[admin@10 ~]$ podman pull localhost
? Please select an image:
▸ registry.access.redhat.com/localhost:latest
registry.fedoraproject.org/localhost:latest
registry.centos.org/localhost:latest
docker.io/library/localhost:latest
The command triggers an output for displaying options available to select pulling the image from certain image repository. The above command execution of ‘podman pull localhost’ actually triggering a specific output. The output is a list of the address of image repositories. Those address actually appears according the container’s configuration file. That container’s configuration file exist in ‘/etc/containers/registries.conf’. Actually, there is a change from the original configuration. So, the original configuration for defining the list of the image repository server exist as follows :
unqualified-search-registries = ["registry.fedoraproject.org", "registry.access.redhat.com", "registry.centos.org", "docker.io"]
But for some experiment purpose, the above format which is the v2 configuration syntax pattern for defining the list of image repository server is changed. The experiment attempt to solve an error message appears upon pulling image using podman. Below is actually the v1 configuration syntax pattern for defining list of the the image repository server :
[registries.search] registries = ['registry.access.redhat.com','registry.fedoraproject.org','registry.centos.org','docker.io']
Basically, the above ‘podman pull localhost’ command is giving an option to choose the image repository where the image is going to be pulled. Just move the top and bottom arrow button to select the image repository. The following is the execution of the command by selecting the first choice in the list of image repositories :
[admin@10 ~]$ podman pull localhost ✔ registry.access.redhat.com/localhost:latest Trying to pull registry.access.redhat.com/localhost:latest... name unknown: Repo not found Error: Error initializing source docker://registry.access.redhat.com/localhost:latest: Error reading manifest latest in registry.access.redhat.com/localhost: name unknown: Repo not found [admin@10 ~]$
So, there is an error message appear as ‘name unknown: Repo not found’. But another error message also appear at the end. That error message is ‘Error reading manifest latest in registry.access.redhat.com/localhost’. Basically it is the same error message appear in the article with the title of ‘How to Solve Error Message manifest unknown: manifest unknown when executing podman to pull image’ in this link.
The differentiation between it aside from the error message appears although it is the same process for pulling the image using podman is just the configuration. The article with the title of ‘How to Solve Error Message manifest unknown: manifest unknown when executing podman to pull image’ in this link is using the v2 format configuration syntax pattern for listing image server repository. On the other hand, this article is using the v1 format configuration syntax pattern instead.
Solution
The solution is actually simple. It has the same solution with the other article with the title of ‘How to Solve Error Message manifest unknown: manifest unknown when executing podman to pull image’ in this link. Basically the error appear because there is no image with the name of it at the first place. So, it will be wise to search it first before actually pulling it. Just execute the following command to search it :
[admin@10 ~]$ podman search registry.access.redhat.com/localhost [admin@10 ~]$
It is also the case if the image exist as in the following command execution :
[admin@10 ~]$ podman search registry.access.redhat.com/mysql INDEX NAME DESCRIPTION STARS OFFICIAL AUTOMATED redhat.com registry.access.redhat.com/rhscl/mysql-57-rhel7 Docker image for running MySQL 5.7 server. T... 0 redhat.com registry.access.redhat.com/rhscl/mysql-56-rhel7 MySQL 5.6 SQL database server 0 redhat.com registry.access.redhat.com/openshift3/mysql-55-rhel7 MySQL 5.5 SQL database server 0 redhat.com registry.access.redhat.com/openshift3/mysql-apb Ansible Playbook Bundle application definiti... 0 redhat.com registry.access.redhat.com/rhmap44/mysql Provides an extension to the RHSCL MySQL Doc... 0 redhat.com registry.access.redhat.com/rhmap42/mysql Provides an extension to the RHSCL MySQL Doc... 0 redhat.com registry.access.redhat.com/rhmap43/mysql Provides an extension to the RHSCL MySQL Doc... 0 redhat.com registry.access.redhat.com/rhmap46/mysql Provides an extension to the RHSCL MySQL ima... 0 redhat.com registry.access.redhat.com/rhmap45/mysql Provides an extension to the RHSCL MySQL ima... 0 redhat.com registry.access.redhat.com/rhmap47/mysql Provides an extension to the RHSCL MySQL ima... 0 redhat.com registry.access.redhat.com/rhscl/mysql-80-rhel7 This container image provides a containerize... 0 [admin@10 ~]$
If the image name do exist, just start pulling the image back using podman as in the previous command execution.