.nh .TH podman\-pull(1) .SH NAME .PP podman\-pull \- Pull an image from a registry .SH SYNOPSIS .PP \fBpodman pull\fP [\fIoptions\fP] \fIsource\fP .PP \fBpodman image pull\fP [\fIoptions\fP] \fIsource\fP .PP \fBpodman pull\fP [\fIoptions\fP] [\fItransport\fP]\fIname\fP[:\fItag\fP|@\fIdigest\fP] .PP \fBpodman image pull\fP [\fIoptions\fP] [\fItransport\fP]\fIname\fP[:\fItag\fP|@\fIdigest\fP] .SH DESCRIPTION .PP Copies an image from a registry onto the local machine. \fBpodman pull\fP pulls an image from Docker Hub if a registry is not specified in the command line argument. If an image tag is not specified, \fBpodman pull\fP defaults to the image with the \fBlatest\fP tag (if it exists) and pulls it. After the image is pulled, podman will print the full image ID. \fBpodman pull\fP can also pull an image using its digest \fBpodman pull\fP \fIimage\fP@\fIdigest\fP\&. \fBpodman pull\fP can be used to pull images from archives and local storage using different transports. .SH Image storage .PP Images are stored in local image storage. .SH SOURCE .PP The SOURCE is the location from which the container images are pulled. The Image "SOURCE" uses a "transport":"details" format. Only the \fB\fCdocker\fR (container registry) transport is allowed for remote access. .PP Multiple transports are supported: .PP \fBdir:\fP\fIpath\fP An existing local directory \fIpath\fP storing the manifest, layer tarballs and signatures as individual files. This is a non\-standardized format, primarily useful for debugging or noninvasive container inspection. .PP .RS .nf $ podman pull dir:/tmp/myimage .fi .RE .PP \fBdocker://\fP\fIdocker\-reference\fP (Default) An image reference stored in a remote container image registry. The reference can include a path to a specific registry; if it does not, the registries listed in registries.conf will be queried to find a matching image. By default, credentials from podman login (stored at $XDG\_RUNTIME\_DIR/containers/auth.json by default) will be used to authenticate; if these cannot be found, we will fall back to using credentials in $HOME/.docker/config.json. .PP .RS .nf $ podman pull quay.io/username/myimage .fi .RE .PP \fBdocker\-archive:\fP\fIpath\fP[\fB:\fP\fIdocker\-reference\fP] An image is stored in the \fB\fCdocker save\fR formatted file. \fIdocker\-reference\fP is only used when creating such a file, and it must not contain a digest. .PP .RS .nf $ podman pull docker\-archive:/tmp/myimage .fi .RE .PP \fBdocker\-daemon:\fP\fIdocker\-reference\fP An image in \fIdocker\-reference\fP format stored in the docker daemon internal storage. The \fIdocker\-reference\fP can also be an image ID (docker\-daemon:algo:digest). .PP .RS .nf $ sudo podman pull docker\-daemon:docker.io/library/myimage:33 .fi .RE .PP \fBoci\-archive:\fP\fIpath\fP\fB:\fP\fItag\fP An image \fItag\fP in a directory compliant with "Open Container Image Layout Specification" at \fIpath\fP\&. .PP .RS .nf $ podman pull oci\-archive:/tmp/myimage .fi .RE .SH OPTIONS .SS \fB\-\-all\-tags\fP, \fBa\fP .PP All tagged images in the repository will be pulled. .PP Note: When using the all\-tags flag, Podman will not iterate over the search registries in the containers\-registries.conf(5) but will always use docker.io for unqualified image names. .SS \fB\-\-arch\fP=\fIARCH\fP .PP Override the architecture, defaults to hosts, of the image to be pulled. For example, \fB\fCarm\fR\&. .SS \fB\-\-authfile\fP=\fIpath\fP .PP Path of the authentication file. Default is ${XDG\_RUNTIME\_DIR}/containers/auth.json, which is set using \fB\fCpodman login\fR\&. If the authorization state is not found there, $HOME/.docker/config.json is checked, which is set using \fB\fCdocker login\fR\&. .PP Note: You can also override the default path of the authentication file by setting the REGISTRY\_AUTH\_FILE environment variable. \fB\fCexport REGISTRY\_AUTH\_FILE=path\fR .SS \fB\-\-cert\-dir\fP=\fIpath\fP .PP Use certificates at \fIpath\fP (*\&.crt, *\&.cert, *\&.key) to connect to the registry. Default certificates directory is \fI/etc/containers/certs.d\fP\&. (Not available for remote commands) .SS \fB\-\-creds\fP=\fI[username[:password]]\fP .PP The [username[:password]] to use to authenticate with the registry if required. If one or both values are not supplied, a command line prompt will appear and the value can be entered. The password is entered without echo. .SS \fB\-\-disable\-content\-trust\fP .PP This is a Docker specific option to disable image verification to a Docker registry and is not supported by Podman. This flag is a NOOP and provided solely for scripting compatibility. .SS \fB\-\-help\fP, \fB\-h\fP .PP Print usage statement .SS \fB\-\-os\fP=\fIOS\fP .PP Override the OS, defaults to hosts, of the image to be pulled. For example, \fB\fCwindows\fR\&. .SS \fB\-\-platform\fP=\fIOS/ARCH\fP .PP Specify the platform for selecting the image. (Conflicts with \-\-arch and \-\-os) The \fB\fC\-\-platform\fR option can be used to override the current architecture and operating system. .SS \fB\-\-quiet\fP, \fB\-q\fP .PP Suppress output information when pulling images .SS \fB\-\-tls\-verify\fP=\fItrue|false\fP .PP Require HTTPS and verify certificates when contacting registries (default: true). If explicitly set to true, then TLS verification will be used. If set to false, then TLS verification will not be used. If not specified, TLS verification will be used unless the target registry is listed as an insecure registry in registries.conf. .SS \fB\-\-variant\fP=\fIVARIANT\fP .PP Use \fIVARIANT\fP instead of the default architecture variant of the container image. Some images can use multiple variants of the arm architectures, such as arm/v5 and arm/v7. .SH EXAMPLES .PP .RS .nf $ podman pull alpine:latest Trying to pull registry.access.redhat.com/alpine:latest... Failed Trying to pull registry.fedoraproject.org/alpine:latest... Failed Trying to pull docker.io/library/alpine:latest...Getting image source signatures Copying blob sha256:88286f41530e93dffd4b964e1db22ce4939fffa4a4c665dab8591fbab03d4926 1.90 MB / 1.90 MB [========================================================] 0s Copying config sha256:76da55c8019d7a47c347c0dceb7a6591144d232a7dd616242a367b8bed18ecbc 1.48 KB / 1.48 KB [========================================================] 0s Writing manifest to image destination Storing signatures 04660052281190168dbb2362eb15bf7067a8dc642d2498055e0e72efa961a4b6 .fi .RE .PP .RS .nf $ podman pull alpine@sha256:d7342993700f8cd7aba8496c2d0e57be0666e80b4c441925fc6f9361fa81d10e Trying to pull docker.io/library/alpine@sha256:d7342993700f8cd7aba8496c2d0e57be0666e80b4c441925fc6f9361fa81d10e... Getting image source signatures Copying blob 188c0c94c7c5 done Copying config d6e46aa247 done Writing manifest to image destination Storing signatures d6e46aa2470df1d32034c6707c8041158b652f38d2a9ae3d7ad7e7532d22ebe0 .fi .RE .PP .RS .nf $ podman pull \-\-authfile temp\-auths/myauths.json docker://docker.io/umohnani/finaltest Trying to pull docker.io/umohnani/finaltest:latest...Getting image source signatures Copying blob sha256:6d987f6f42797d81a318c40d442369ba3dc124883a0964d40b0c8f4f7561d913 1.90 MB / 1.90 MB [========================================================] 0s Copying config sha256:ad4686094d8f0186ec8249fc4917b71faa2c1030d7b5a025c29f26e19d95c156 1.41 KB / 1.41 KB [========================================================] 0s Writing manifest to image destination Storing signatures 03290064078cb797f3e0a530e78c20c13dd22a3dd3adf84a5da2127b48df0438 .fi .RE .PP .RS .nf $ podman pull \-\-creds testuser:testpassword docker.io/umohnani/finaltest Trying to pull docker.io/umohnani/finaltest:latest...Getting image source signatures Copying blob sha256:6d987f6f42797d81a318c40d442369ba3dc124883a0964d40b0c8f4f7561d913 1.90 MB / 1.90 MB [========================================================] 0s Copying config sha256:ad4686094d8f0186ec8249fc4917b71faa2c1030d7b5a025c29f26e19d95c156 1.41 KB / 1.41 KB [========================================================] 0s Writing manifest to image destination Storing signatures 03290064078cb797f3e0a530e78c20c13dd22a3dd3adf84a5da2127b48df0438 .fi .RE .PP .RS .nf $ podman pull \-\-tls\-verify=false \-\-cert\-dir image/certs docker.io/umohnani/finaltest Trying to pull docker.io/umohnani/finaltest:latest...Getting image source signatures Copying blob sha256:6d987f6f42797d81a318c40d442369ba3dc124883a0964d40b0c8f4f7561d913 1.90 MB / 1.90 MB [========================================================] 0s Copying config sha256:ad4686094d8f0186ec8249fc4917b71faa2c1030d7b5a025c29f26e19d95c156 1.41 KB / 1.41 KB [========================================================] 0s Writing manifest to image destination Storing signatures 03290064078cb797f3e0a530e78c20c13dd22a3dd3adf84a5da2127b48df0438 .fi .RE .PP .RS .nf $ podman pull \-\-arch=arm arm32v7/debian:stretch Trying to pull docker.io/arm32v7/debian:stretch... Getting image source signatures Copying blob b531ae4a3925 done Copying config 3cba58dad5 done Writing manifest to image destination Storing signatures 3cba58dad5d9b35e755b48b634acb3fdd185ab1c996ac11510cc72c17780e13c .fi .RE .SH FILES .PP \fBregistries.conf\fP (\fB\fC/etc/containers/registries.conf\fR) .PP .RS .nf registries.conf is the configuration file which specifies which container registries should be consulted when completing image names which do not include a registry or domain portion. .fi .RE .PP NOTE: Use the environment variable \fB\fCTMPDIR\fR to change the temporary storage location of downloaded container images. Podman defaults to use \fB\fC/var/tmp\fR\&. .SH SEE ALSO .PP podman(1), podman\-push(1), podman\-login(1), containers\-registries.conf(5) .SH HISTORY .PP July 2017, Originally compiled by Urvashi Mohnani umohnani@redhat.com \[la]mailto:umohnani@redhat.com\[ra]