buildah-manifest-push(1)

okay bestie, this is the buildah-manifest-push(1) page from the General Commands Manual, and it's literally about pushing a manifest list or image index to a registry. no cap, every flag is still here. let's get into it 💖

🎀 NAME 🎀

buildah-manifest-push — push a manifest list or image index to a registry. that's the whole vibe, but the details are below, bestie.

✨ SYNOPSIS ✨

buildah manifest push [options...] listNameOrIndexName transport:details

🌸 DESCRIPTION 🌸

Pushes a manifest list or image index to a registry. literally that. if you're holding a list/index and you want it in a registry, this is the main character command 💅

⭐ RETURN VALUE ⭐

You get back the list image's ID and the digest of the image's manifest. keep those receipts, iykyk 🫶

💖 OPTIONS 💖

• --add-compression compression — makes sure the requested compression variant for each platform gets added to the manifest list while keeping the original instance intact in that same manifest list. supported values are gzip, zstd and zstd:chunked.

note: this is different from --compression, which replaces the instance with the requested one using the specified compression, while --add-compression makes sure each instance has its variant added to the manifest list without modifying the original instance. yes, that distinction is real — don't skip it 🫡

• --all — push the images mentioned in the manifest list or image index, in addition to the list or index itself. default is true. so yes, by default it does the extra thing too.
• --authfile path — path of the authentication file. default is ${XDG_RUNTIME_DIR}/containers/auth.json, which is set using buildah login. if the authorization state is not found there, $HOME/.docker/config.json is checked, which is set using docker login.
• --cert-dir path — use certificates at path (*.crt, *.cert, *.key) to connect to the registry. the default certificates directory is /etc/containers/certs.d.
• --compression-format format — specifies the compression format to use. supported values are: gzip, zstd and zstd:chunked.
• --compression-level level — specify the compression level used with the compression (a.k.a. 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). numbers matter, bestie 🔥
• --creds creds — 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. privacy slay 🙈
• --digestfile Digestfile — after copying the image, write the digest of the resulting image to the file.
• --force-compression — if set, push uses the specified compression algorithm even if the destination contains a differently-compressed variant already. defaults to true if --compression-format is explicitly specified on the command-line, false otherwise.
• --format, -f — manifest list type (oci or v2s2) to use when pushing the list (default is oci).
• --quiet, -q — don't output progress information when pushing lists.
• --remove-signatures — don't copy signatures when pushing images.
• --retry attempts — number of times to retry in case of failure when performing push of images to registry. defaults to 3.
• --retry-delay duration — duration of delay between retry attempts in case of failure when performing push of images to registry. defaults to 2s.
• --rm — delete the manifest list or image index from local storage if pushing succeeds.
• --sign-by fingerprint — sign the pushed images using the GPG key that matches the specified fingerprint.
• --timestamp seconds — set the "created" timestamp for outputs to this number of seconds since the epoch (Unix time 0, i.e., 00:00:00 UTC on 1 January 1970) (defaults to current time). for example, if an oci-archive output is used, the tar entries created times are set to this value.
• --tls-verify bool-value — 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.

🦋 EXAMPLE 🦋

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

👑 SEE ALSO 👑

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)

---

that's the whole page, bestie 🫶 source/version: buildah · date: September 2019 · page: buildah-manifest-push(1) — go push that list and slay 💅✨