.nh
.TH podman-manifest-push 1
.SH NAME
.PP
podman-manifest-push - Push a manifest list or image index to a registry

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

.SH DESCRIPTION
.PP
Pushes a manifest list or image index to a registry.

.SH RETURN VALUE
.PP
The list image's ID and the digest of the image's manifest.

.SH OPTIONS
.SS \fB--all\fP
.PP
Push the images mentioned in the manifest list or image index, in addition to
the list or index itself. (Default true)

.SS \fB--authfile\fP=\fIpath\fP
.PP
Path of the authentication file. Default is \fB\fC${XDG_RUNTIME_DIR}/containers/auth.json\fR, which is set using \fBpodman login\fP\&.
If the authorization state is not found there, \fB\fC$HOME/.docker/config.json\fR is checked, which is set using \fBdocker login\fP\&.

.PP
Note: There is also the option to override the default path of the authentication file by setting the \fB\fCREGISTRY_AUTH_FILE\fR environment variable. This can be done with \fBexport REGISTRY_AUTH_FILE=\fIpath\fP\fP\&.

.SS \fB--cert-dir\fP=\fIpath\fP
.PP
Use certificates at \fIpath\fP (*\&.crt, *\&.cert, *\&.key) to connect to the registry. (Default: /etc/containers/certs.d)
Please refer to \fBcontainers-certs.d(5)\fP for details.
(This option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines)

.SS \fB--compression-format\fP=\fBgzip\fP | \fIzstd\fP | \fIzstd:chunked\fP
.PP
Specifies the compression format to use.  Supported values are: \fB\fCgzip\fR, \fB\fCzstd\fR and \fB\fCzstd:chunked\fR\&.  The default is \fB\fCgzip\fR unless overridden in the containers.conf file.

.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--digestfile\fP=\fIDigestfile\fP
.PP
After copying the image, write the digest of the resulting image to the file.
(This option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines)

.SS \fB--format\fP, \fB-f\fP=\fIformat\fP
.PP
Manifest list type (oci or v2s2) to use when pushing the list (default is oci).

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

.SS \fB--remove-signatures\fP
.PP
Don't copy signatures when pushing images.

.SS \fB--rm\fP
.PP
Delete the manifest list or image index from local storage if pushing succeeds.

.SS \fB--sign-by\fP=\fIfingerprint\fP
.PP
Sign the pushed images with a “simple signing” signature using the specified key. (This option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines)

.SS \fB--sign-by-sigstore-private-key\fP=\fIpath\fP
.PP
Sign the pushed images with a sigstore signature using a private key at the specified path. (This option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines)

.SS \fB--sign-passphrase-file\fP=\fIpath\fP
.PP
If signing the image (using either \fB--sign-by\fP or \fB--sign-by-sigstore-private-key\fP), read the passphrase to use from the specified path.

.SS \fB--tls-verify\fP
.PP
Require HTTPS and verify certificates when contacting registries (default: \fBtrue\fP).
If explicitly set to \fBtrue\fP, TLS verification will be used.
If set to \fBfalse\fP, 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 \fBcontainers-registries.conf(5)\fP

.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 manifest push mylist:v1.11 dir:/tmp/mylist

.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 manifest push mylist:v1.11 docker://registry.example.org/mylist:v1.11

.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 manifest push mylist:v1.11 docker-archive:/tmp/mylist

.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
$ podman manifest push mylist:v1.11 docker-daemon:registry.example.org/mylist:v1.11

.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 manifest push mylist:v1.11 oci-archive:/tmp/mylist

.fi
.RE

.SH EXAMPLE
.PP
.RS

.nf
podman manifest push mylist:v1.11 docker://registry.example.org/mylist:v1.11

.fi
.RE

.SH SEE ALSO
.PP
\fBpodman(1)\fP, \fBpodman-manifest(1)\fP