INCUS.STORAGE.BUCKET.CREATE(1)

πŸ’– NAME πŸ’–

incus-storage-bucket-create β€” bestie, this is the one that creates brand new custom storage buckets. Not a bucket you inherit, not a bucket you borrow β€” a fresh, custom, yours-to-keep bucket. πŸͺ£βœ¨


✨ SYNOPSIS ✨

incus storage bucket create [:]  [=...] [flags]

🌸 DESCRIPTION 🌸

So basically the whole vibe here is:

Create new custom storage buckets. That's it, that's the job. You roll up, you name a pool, you name a bucket, and the bucket simply exists now. Main character energy for a storage primitive, honestly. πŸ’…


πŸŽ€ OPTIONS πŸŽ€

  • --description="" β€” your bucket deserves lore. Drop a bucket description here (default is "", aka nothing, aka mystery bucket). πŸ¦‹
  • --target="" β€” the cluster member name. Point this at a specific member of the cluster, default is "". πŸ“

πŸ‘‘ OPTIONS INHERITED FROM PARENT COMMANDS πŸ‘‘

These are the family heirlooms, they come down from the parent command. You didn't ask for them, but they're here and they're iconic.

  • --debug[=false] β€” show all the debug messages. Every last one. No secrets. πŸ’€
  • --explain[=false] β€” if the command is valid, it explains its parsed arguments instead of actually running it. Like a dress rehearsal, but for flags. 🎭
  • --force-local[=false] β€” force using the local unix socket. Local only, no traveling. 🏠
  • -h, --help[=false] β€” print help. Your classic cry-for-clarity button. 🫢
  • --project="" β€” override the source project. Default is "". πŸ“
  • -q, --quiet[=false] β€” don't show progress information. Silence is golden, fr fr. 🀫
  • --sub-commands[=false] β€” use this with help or --help to view sub-commands. It's the peeking-behind-the-curtain flag. πŸ‘€
  • -v, --verbose[=false] β€” show all information messages. Chatty era activated. πŸ—£οΈ
  • --version[=false] β€” print version number. Who are you, really. πŸ”’

πŸ”₯ EXAMPLE πŸ”₯

Making a bucket from nothing:

incus storage bucket create p1 b01
     Create a new storage bucket named b01 in storage pool p1

Making a bucket with a config glow-up piped in from a file:

incus storage bucket create p1 b01 < config.yaml
     Create a new storage bucket named b01 in storage pool p1 using the content of config.yaml
Not me feeding a bucket a config.yaml like it's a little snack. 😭 That second one pipes the content of config.yaml straight in as stdin, so the bucket gets born pre-configured. Slay.

🌈 SEE ALSO 🌈

  • incus-storage-bucket(1) β€” go read the parent, it's giving ✨ context ✨ (iykyk)

πŸ“œ HISTORY πŸ“œ

24-Sep-2026 β€” Auto generated by spf13/cobra. Conjured, not hand-written. 🧚


Okay bestie, that's the whole page, and here's the cute lil' sign-off: this manual was auto generated by spf13/cobra, dated Sep 2026, and it belongs to Incus - Command line client(1). Go make some buckets. πŸͺ£πŸ’–

πŸ“¦ where this page comes from