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, --all is the "bring everyone" option πŸ™ˆ
  • --amend β€” instead of exiting with an error when listNameOrIndexName already exists, it amends the existing image. some deets: when listNameOrIndexName is a manifest list, the contents of listNameOrIndexName are not modified unless imageNames are given. and when listNameOrIndexName is 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 named listNameOrIndexName already exists, this removes the name from the existing image before creating the new manifest list.
πŸ’€ heads up bestie: --replace cannot 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 to true. 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