containers...rage-exists(1)

✨ NAME ✨

okay so bestie, welcome to containers...rage-exists(1) β€” yes that's the manual page name, we're keeping it πŸ’… β€” and the actual command it's all about is containers-storage-exists, aka Check if a layer, image, or container exists. that's the whole vibe. does the thing exist? let's find out πŸ¦‹


🌸 SYNOPSIS 🌸

containers-storage exists [options [...]]
layerOrImageOrContainerNameOrID [...]

so you're calling containers-storage exists, you can throw some options at it, and then you hand it one or more names or IDs of layers, images, or containers. that's it, that's the move πŸŽ€


πŸ’– DESCRIPTION πŸ’–

Checks if there are layers, images, or containers which have the specified names or IDs.

like... it looks at the names/IDs you gave it and tells you whether matching layers, images, or containers actually exist. a little existence check. a vibe check, if you will ✨


πŸ‘‘ OPTIONS πŸ‘‘

  • -c, --container β€” Only succeed if the names or IDs are that of containers. so if you pass a layer or an image name, it's not gonna succeed, bestie πŸ™ˆ containers only, no cap.
  • -i, --image β€” Only succeed if the names or IDs are that of images. images only, periodt. anything else? nope πŸ’€
  • -l, --layer β€” Only succeed if the names or IDs are that of layers. layers only, that's the assignment 🌈
  • -q, --quiet β€” Suppress output. shhh 🀫 no talking, just vibes (and the exit status, iykyk).

🧚 EXAMPLE 🧚

containers-storage exists my-base-layer

look at her go πŸ’œ checking if my-base-layer exists. iconic behaviour, honestly.


lowkey reminder: these options are strict about what kind of thing your name/ID is β€” -c, -i, and -l each make success depend on it being a container, an image, or a layer respectively. no mixing, no matching, no exceptions πŸ’…

and that's the page!! 🌸 this lil slice of documentation is from August 2016, and it lives under the manual name containers...rage-exists(1) 🫢 mwah, go check if your stuff exists bestie πŸ’–βœ¨

πŸ“¦ where this page comes from