.nh
.TH buildah-manifest-push "1" "September 2019" "buildah"
.SH NAME
.PP
buildah-manifest-push - Push a manifest list or image index to a registry.

.SH SYNOPSIS
.PP
\fBbuildah manifest push\fP [options...] \fIlistNameOrIndexName\fP \fItransport:details\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
.PP
\fB--add-compression\fP \fIcompression\fP

.PP
Makes sure that requested compression variant for each platform is added to the manifest list keeping original instance
intact in the same manifest list. Supported values are (\fBgzip\fR, \fBzstd\fR and \fBzstd:chunked\fR)

.PP
Note: This is different than \fB--compression\fR which replaces the instance with requested with specified compression
while \fB--add-compression\fR makes sure than each instance has it variant added to manifest list without modifying the
original instance.

.PP
\fB--all\fP

.PP
Push the images mentioned in the manifest list or image index, in addition to
the list or index itself.

.PP
\fB--authfile\fP \fIpath\fP

.PP
Path of the authentication file. Default is ${XDG_RUNTIME_DIR}/containers/auth.json, which is set using \fBbuildah login\fR\&.
If the authorization state is not found there, $HOME/.docker/config.json is checked, which is set using \fBdocker login\fR\&.

.PP
\fB--cert-dir\fP \fIpath\fP

.PP
Use certificates at \fIpath\fP (*\&.crt, *\&.cert, *\&.key) to connect to the registry.
The default certificates directory is \fI/etc/containers/certs.d\fP\&.

.PP
\fB--compression-format\fP \fIformat\fP

.PP
Specifies the compression format to use.  Supported values are: \fBgzip\fR, \fBzstd\fR and \fBzstd:chunked\fR\&.

.PP
\fB--compression-level\fP \fIlevel\fP

.PP
Specify the compression level used with the compression.

.PP
Specifies the compression level to use.  The value is specific to the compression algorithm used, e.g. for zstd the accepted values are in the range 1-20 (inclusive), while for gzip it is 1-9 (inclusive).

.PP
\fB--creds\fP \fIcreds\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.

.PP
\fB--digestfile\fP \fIDigestfile\fP

.PP
After copying the image, write the digest of the resulting image to the file.

.PP
\fB--force-compression\fP

.PP
If set, push uses the specified compression algorithm even if the destination contains a differently-compressed variant already.
Defaults to \fBtrue\fR if \fB--compression-format\fR is explicitly specified on the command-line, \fBfalse\fR otherwise.

.PP
\fB--format\fP, \fB-f\fP

.PP
Manifest list type (oci or v2s2) to use when pushing the list (default is oci).

.PP
\fB--quiet\fP, \fB-q\fP

.PP
Don't output progress information when pushing lists.

.PP
\fB--remove-signatures\fP

.PP
Don't copy signatures when pushing images.

.PP
\fB--rm\fP

.PP
Delete the manifest list or image index from local storage if pushing succeeds.

.PP
\fB--sign-by\fP \fIfingerprint\fP

.PP
Sign the pushed images using the GPG key that matches the specified fingerprint.

.PP
\fB--tls-verify\fP \fIbool-value\fP

.PP
Require HTTPS and verification of certificates when talking to container registries (defaults to true).  TLS verification cannot be used when talking to an insecure registry.

.SH EXAMPLE
.EX
buildah manifest push mylist:v1.11 registry.example.org/mylist:v1.11

.EE

.SH SEE ALSO
.PP
buildah(1), buildah-login(1), buildah-manifest(1), buildah-manifest-create(1), buildah-manifest-add(1), buildah-manifest-remove(1), buildah-manifest-annotate(1), buildah-manifest-inspect(1), buildah-rmi(1), docker-login(1)