containers...-image-data(1)

✨ NAME ✨

okay bestie, welcome to containers...-image-data(1) πŸ’– β€” this is the manual for containers-storage-set-image-data, and yes, its whole entire job is: Set lookaside data for an image. that's it. that's the gig. iconic behavior honestly πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

containers-storage set-image-data [options [...]] imageNameOrID dataName

so you got your options (optional, they're optional bestie), you got your imageNameOrID, you got your dataName. three little slots and you're slaying πŸ’…


🌸 DESCRIPTION 🌸

Sets a piece of named data which is associated with an image.

lowkey that's the whole vibe: you're attaching one named lil blob of data to one image. it's giving "sticky note on the fridge" but for containers 🧚 no cap.


✨ OPTIONS ✨

  • -f, --file filename β€” read the data contents from a file instead of stdin. like, instead of piping stuff in with your little keyboard hands, you just point at a file and say "that one, bestie" πŸ“

πŸ’œ EXAMPLE πŸ’œ

here's how you actually do the thing:

containers-storage set-image-data -f ./manifest.json my-image manifest

see how we're grabbing the contents from ./manifest.json, dropping it onto my-image, and calling that data slot manifest? obsessed. that's the pattern. periodt πŸ‘‘


πŸ”₯ SEE ALSO πŸ”₯

go read these too, they're the friend group:


ngl if you skipped straight to the bottom looking for a tldr: set the data, name the data, done. πŸ’€

anyway that's the whole page babes β€” this one came out of the General Commands Manual for containers...-image-data(1), dated August 2016, and it still eats fr fr 🫢

πŸ“¦ where this page comes from