The translation is temporarily closed for contributions due to maintenance, please come back later.
Images and Containers
Finding Images
Search for images with a keyword:
$ podman search fedora
$ podman search homeassistant
The registries which will be searched are configured in the /etc/containers/registry.conf file.
The resulting name will include both the registry location and the name of the image.
The registry name may include a port number.
The image name consists of USER/REPO. The user can be an individual, team, or company that uploads the images to the registry.
The image repository contains tagged images and hidden layers. Most repositories contain an image with the tag of 'latest'.
When downloading an image with pull, run, or build commands, you may specify a specific tag image. The default is to pull the image tagged 'latest'.
The[`skopeo`] command is a utility to work with images in many different container environments. It was created to view information in remote registries and is now a command and library for copying images with different transports. It is used to manage container images and image storage remotely and locally and all without requiring root. It can also pass authentication credentials when required by the repository.
View creation dates, architectures, labels, tags, and layer checksums of a remote image repository:
$ skopeo inspect docker://
Manage Local Images
When you run a container, the image is first downloaded to the local system. It can be helpful to go ahead and download an image as a separate command.
The default is to pull the latest image from the default registry:
$ podman pull fedora
You can also specify the registry, user, tag, or, as in the following example, some combination:
$ podman pull
List the local images: