podman-manifest-create(1)
β¨ podman-manifest-create β bestie's guide to making manifest lists β¨
okay so you're in the podman-manifest-create(1) page, which is part of the podman General Commands Manual, and we're about to create manifest lists / image indexes together. it's giving build-a-bear but for multi-arch images π§Έπ
πΈ NAME πΈ
podman-manifest-create β make a manifest list or an image index. yes, that's the whole vibe. creating. manifests. lists. iconic.
π¦ SYNOPSIS π¦
podman manifest create [options] listnameorindexname [imagename ...]
π DESCRIPTION π
So basically: this makes a brand-new manifest list and stores it in your local storage under whatever name you gave it. slay.
And if you pass extra images along? They get added to that freshly-created list or index. no cap. π«Ά
π OPTIONS π
--allβ if any of the images you're adding to your new list or index are themselves lists or indexes, this adds all of their contents. by default you only get one image from such a list added to your new list or index. so--allis the "give me everything" button π₯--amend,-aβ if a manifest list named listnameorindexname already exists, this modifies the preexisting list instead of just exiting with an error. cute, right? BUT β and listen β the contents of listnameorindexname are not modified if you don't give any *imagename*s. so no sneaky changes with zero arguments, periodt.--annotation=valueβ set an annotation on the newly-created image index. label it, decorate it, make it yours π--tls-verifyβ require HTTPS and verify certificates when contacting registries (default: true). here's the breakdown bestie:- if you explicitly set it to true, TLS verification is used.
- if you set it to false, TLS verification is not used.
- if you don't specify it at all, TLS verification is used β unless the target registry is listed as an insecure registry in
containers-registries.conf(5).
ngl, that last one is the plot twist. insecure registries get a free pass when you don't say anything, so know your config π
π EXAMPLES π
Create the specified manifest.
podman manifest create mylist:v1.11
9cfd24048d5fc80903f088f1531a21bff01172abe66effa8941a4c2308dc745f
Create the specified manifest manifest or modify it if it previously exist.
(that's literally what the page says, i'm not fixing it, i'm just relaying it π)
podman manifest create --amend mylist:v1.11
9cfd24048d5fc80903f088f1531a21bff01172abe66effa8941a4c2308dc745f
Create the named manifest including the specified image matching the current platform.
podman manifest create mylist:v1.11 docker://fedora
5c2bc76bfb4ba6665a7973f7e1c05ee0536b4580637f27adc9fa5a4b2bc03cf1
Create the named manifest including all images referred to with the specified image reference.
podman manifest create --all mylist:v1.11 docker://fedora
30330571e79c65288a4fca421d9aed29b0210d57294d9c2056743fdcf6e3967b
π§ SEE ALSO π§
and that's the whole page, bestie!! π this was the podman-manifest-create(1) manual page from the General Commands Manual β go forth and manifest (literally) β¨π¦πΈ
mwah, drink some water, and remember: --amend is your friend but only if you bring an image π
π¦ where this page comes from
- arch rolling: podman-docker 6.1.4-1 Β· Apache-2.0
- fedora 43: podman-docker 5:5.6.2-1.fc43 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- fedora 43: podman-docker 5:5.8.4-1.fc43
- fedora 43: podman-docker 5:5.8.8-1.fc43
- fedora 43: podman-docker 5:5.8.9-1.fc43 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- fedora 44: podman-docker 5:5.8.1-1.fc44 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- fedora 44: podman-docker 5:5.8.7-1.fc44
- fedora 44: podman-docker 5:5.8.9-1.fc44 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- ubuntu resolute: podman-docker 5.7.0+ds2-3build1 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms