podman-manifest(1)

💖 podman-manifest(1) — bestie edition 💖

okay so you found the podman-manifest page in the General Commands Manual and honestly? iconic. this is the group chat where we talk about creating and manipulating manifest lists and image indexes. pull up a chair, grab a boba 🧋

---

✨ NAME ✨

podman-manifest — Create and manipulate manifest lists and image indexes

---

🌸 SYNOPSIS 🌸

podman manifest subcommand

---

🦋 DESCRIPTION 🦋

The podman manifest command is basically a whole lil family of subcommands, and you can use them to:

• Create a working Docker manifest list or OCI image index.

that's the vibe. that's the whole assignment. 💅

---

👑 SUBCOMMANDS 👑

every single one of these is its own moment, so let's go one by one:

• add — man page: podman-manifest-add(1) — Add an image or artifact to a manifest list or image index. 🫶
• annotate — man page: podman-manifest-annotate(1) — Add and update information about an image or artifact in a manifest list or image index. ✨
• create — man page: podman-manifest-create(1) — Create a manifest list or image index. 🌱
• exists — man page: podman-manifest-exists(1) — Check if the given manifest list exists in local storage 👀
• inspect — man page: podman-manifest-inspect(1) — Display a manifest list or image index. 🔍
• push — man page: podman-manifest-push(1) — Push a manifest list or image index to a registry. 🚀
• remove — man page: podman-manifest-remove(1) — Remove an item from a manifest list or image index. 🗑️
• rm — man page: podman-manifest-rm(1) — Remove manifest list or image index from local storage. 💀

---

🎀 EXAMPLES 🎀

🌈 Building a multi-arch manifest list from a Containerfile

so real talk: assuming the Containerfile uses RUN instructions, the host needs a way to execute non-native binaries. how you configure that is beyond the scope of this example, bestie — we're not getting into it here. but building a multi-arch manifest list shazam in parallel across 4-threads can be done like this:

$ platarch=linux/amd64,linux/ppc64le,linux/arm64,linux/s390x
$ podman build --jobs=4 --platform=$platarch --manifest shazam .

Note: The --jobs argument is optional. Do not use the podman build command's --tag (or -t) option when building a multi-arch manifest list. not me warning you twice, but like… fr fr. 🙈

---

🌟 Assembling a multi-arch manifest from separately built images

assuming example.com/example/shazam:$arch images are built separately on other hosts and pushed to the example.com registry, they may be combined into a manifest list, and pushed using a simple loop:

$ REPO=example.com/example/shazam
$ podman manifest create $REPO:latest
$ for IMGTAG in amd64 s390x ppc64le arm64; do
          podman manifest add $REPO:latest docker://$REPO:IMGTAG;
      done
$ podman manifest push --all $REPO:latest

Note: The add instruction argument order is <manifest> then <image>. Also, the --all push option is required to ensure all contents are pushed, not just the native platform/arch. the way that --all is not optional here… it's giving mandatory. periodt. 🔥

---

🦄 Removing and tagging a manifest list before pushing

special care is needed when removing and pushing manifest lists, as opposed to the contents. you almost always want to use the manifest rm and manifest push --all subcommands. for example, a rename and push can be performed like this:

$ podman tag localhost/shazam example.com/example/shazam
$ podman manifest rm localhost/shazam
$ podman manifest push --all example.com/example/shazam

---

💜 SEE ALSO 💜

podman(1), podman-manifest-add(1), podman-manifest-annotate(1), podman-manifest-create(1), podman-manifest-inspect(1), podman-manifest-push(1), podman-manifest-remove(1)

---

and that's the whole page, bestie 💖 the footer just signs it off as podman-manifest(1) — no extra version or date drama attached, just the manual name chillin' at the bottom like a little signature. you ate this. go build something multi-arch. 🫶✨🌈