.nh
.TH podman\-push(1)
.SH NAME
.PP
podman\-push \- Push an image, manifest list or image index from local storage to elsewhere

.SH SYNOPSIS
.PP
\fBpodman push\fP [\fIoptions\fP] \fIimage\fP [\fIdestination\fP]

.PP
\fBpodman image push\fP [\fIoptions\fP] \fIimage\fP [\fIdestination\fP]

.SH DESCRIPTION
.PP
Pushes an image, manifest list or image index from local storage to a specified
destination. Push is mainly used to push images to registries, however
\fBpodman push\fP can be used to save images to tarballs and directories using the
following transports:
\fBdir:\fP, \fBdocker\-archive:\fP, \fBdocker\-daemon:\fP and \fBoci\-archive:\fP\&.

.SH Image storage
.PP
Images are pushed from those stored in local image storage.

.SH DESTINATION
.PP
The DESTINATION is a location to store container images
 The Image "DESTINATION" uses a "transport":"details" format.
 If a transport is not given, podman push will attempt to push
 to a registry.

.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 push myimage dir:/tmp/myimage

.fi
.RE

.PP
\fBdocker://\fP\fIdocker\-reference\fP
  An image in a registry implementing the "Docker Registry HTTP API V2". By default, uses the authorization state in \fB\fC$XDG\_RUNTIME\_DIR/containers/auth.json\fR, which is set using \fB\fC(podman login)\fR\&. If the authorization state is not found there, \fB\fC$HOME/.docker/config.json\fR is checked, which is set using \fB\fC(docker login)\fR\&.

.PP
.RS

.nf
$ podman push myimage 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 push myimage 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. \fIdocker\-reference\fP must contain a tag.

.PP
.RS

.nf
$ sudo podman push myimage 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 push myimage oci\-archive:/tmp/myimage

.fi
.RE

.SH OPTIONS
.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\-\-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\-\-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\-\-compress\fP
.PP
Compress tarball image layers when pushing to a directory using the 'dir' transport. (default is same compression type, compressed or uncompressed, as source)
Note: This flag can only be set when using the \fBdir\fP transport

.SS \fB\-\-digestfile\fP \fIDigestfile\fP
.PP
After copying the image, write the digest of the resulting image to the file.  (Not available for remote commands)

.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\-\-format\fP, \fB\-f\fP=\fIformat\fP
.PP
Manifest Type (oci, v2s1, or v2s2) to use when pushing an image to a directory using the 'dir:' transport (default is manifest type of source)
Note: This flag can only be set when using the \fBdir\fP transport. (Not available for remote commands)

.SS \fB\-\-quiet\fP, \fB\-q\fP
.PP
When writing the output image, suppress progress output

.SS \fB\-\-remove\-signatures\fP
.PP
Discard any pre\-existing signatures in the image. (Not available for remote commands)

.SS \fB\-\-sign\-by\fP=\fIkey\fP
.PP
Add a signature at the destination using the specified key. (Not available for remote commands)

.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.

.SH EXAMPLE
.PP
This example pushes the image specified by the imageID to a local directory in docker format.

.PP
\fB\fC# podman push imageID dir:/path/to/image\fR

.PP
This example pushes the image specified by the imageID to a local directory in oci format.

.PP
\fB\fC# podman push imageID oci\-archive:/path/to/layout:image:tag\fR

.PP
This example pushes the image specified by the imageID to a container registry named registry.example.com

.PP
\fB\fC# podman push imageID docker://registry.example.com/repository:tag\fR

.PP
This example pushes the image specified by the imageID to a container registry named registry.example.com and saves the digest in the specified digestfile.

.PP
\fB\fC# podman push \-\-digestfile=/tmp/mydigest imageID docker://registry.example.com/repository:tag\fR

.PP
This example pushes the image specified by the imageID and puts it into the local docker container store

.PP
\fB\fC# podman push imageID docker\-daemon:image:tag\fR

.PP
This example pushes the alpine image to umohnani/alpine on dockerhub and reads the creds from
the path given to \-\-authfile

.PP
.RS

.nf
# podman push \-\-authfile temp\-auths/myauths.json alpine docker://docker.io/umohnani/alpine
Getting image source signatures
Copying blob sha256:5bef08742407efd622d243692b79ba0055383bbce12900324f75e56f589aedb0
 4.03 MB / 4.03 MB [========================================================] 1s
Copying config sha256:ad4686094d8f0186ec8249fc4917b71faa2c1030d7b5a025c29f26e19d95c156
 1.41 KB / 1.41 KB [========================================================] 1s
Writing manifest to image destination
Storing signatures

.fi
.RE

.PP
This example pushes the rhel7 image to rhel7\-dir with the "oci" manifest type

.PP
.RS

.nf
# podman push \-\-format oci registry.access.redhat.com/rhel7 dir:rhel7\-dir
Getting image source signatures
Copying blob sha256:9cadd93b16ff2a0c51ac967ea2abfadfac50cfa3af8b5bf983d89b8f8647f3e4
 71.41 MB / 71.41 MB [======================================================] 9s
Copying blob sha256:4aa565ad8b7a87248163ce7dba1dd3894821aac97e846b932ff6b8ef9a8a508a
 1.21 KB / 1.21 KB [========================================================] 0s
Copying config sha256:f1b09a81455c351eaa484b61aacd048ab613c08e4c5d1da80c4c46301b03cf3b
 3.01 KB / 3.01 KB [========================================================] 0s
Writing manifest to image destination
Storing signatures

.fi
.RE

.SH SEE ALSO
.PP
podman(1), podman\-pull(1), podman\-login(1)