buildah-manifest-create(1)
π buildah-manifest-create β¨
okay so real talk β this is page buildah-manifest-create(1) from the General Commands Manual, and it's literally the moment your manifest list era begins π
πΈ NAME πΈ
buildah-manifest-create β create a manifest list or image index π
π SYNOPSIS π
buildah manifest create [options...] listNameOrIndexName [imageName ...]
π¦ DESCRIPTION π¦
So what this does is: it creates a brand-new manifest list and stores it as an image in your local storage, using whatever name you gave it. slay β¨
And if you also throw in extra images? They get added to your freshly-created list or index. it's giving instant friend group π«Ά
β RETURN VALUE β
You get back the randomly-generated image ID of the newly-created list or index. iconic. and if you ever need to yeet it, you can delete that image with the buildah rmi command π
β¨ OPTIONS β¨
--allβ if any of the images you're adding to the new list or index are themselves lists or indexes, this adds all of their contents. by default, only one image from such a list gets added to your newly-created list or index. so yeah,--allis the "bring everyone" option π--amendβ instead of exiting with an error whenlistNameOrIndexNamealready exists, it amends the existing image. some deets: whenlistNameOrIndexNameis a manifest list, the contents oflistNameOrIndexNameare not modified unlessimageNamesare given. and whenlistNameOrIndexNameis a regular image, that image gets converted into a manifest list with the original image as its first entry. glow-up behavior, honestly π₯--annotation annotation=valueβ set an annotation on the newly-created image index π·οΈ--replaceβ if an image namedlistNameOrIndexNamealready exists, this removes the name from the existing image before creating the new manifest list.
π heads up bestie:--replacecannot be used together with--amend. pick one, not both, no cap.
--tls-verify bool-valueβ require HTTPS and verification of certificates when talking to container registries. defaults totrue. and real talk: TLS verification cannot be used when talking to an insecure registry π
π§ EXAMPLE π§
buildah manifest create mylist:v1.11
941c1259e4b85bebf23580a044e4838aa3c1e627528422c9bf9262ff1661fca9
buildah manifest create --amend mylist:v1.11
941c1259e4b85bebf23580a044e4838aa3c1e627528422c9bf9262ff1661fca9
buildah manifest create mylist:v1.11 docker://fedora
941c1259e4b85bebf23580a044e4838aa3c1e627528422c9bf9262ff1661fca9
buildah manifest create --all mylist:v1.11 docker://fedora
941c1259e4b85bebf23580a044e4838aa3c1e627528422c9bf9262ff1661fca9
look at that consistency, the same ID every time, she's stable, she's reliable, she's main character energy π
π SEE ALSO π
buildah(1), buildah-manifest(1), buildah-manifest-add(1), buildah-manifest-remove(1), buildah-manifest-annotate(1), buildah-manifest-inspect(1), buildah-manifest-push(1), buildah-rmi(1)
go read the whole fam, iykyk π¦
and that's the whole page, bestie π β brought to you by buildah, dated August 2022, living at buildah-manifest-create(1). mwah, go build something cute πβ¨
π¦ where this page comes from
- centos-stream 10: buildah 2:1.45.0-2.el10 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms