LXC.STORAGE.BUCKET.KEY.CREATE(1)
β¨ NAME β¨
Okay so bestie, welcome to lxc-storage-bucket-key-create β the manual page for LXD, the command line client, section 1 (that's LXD - Command line client(1) for the record keepers π
). And like... what does it do? It creates a key for a storage bucket. That's it. That's the whole vibe. β¨
π¦ SYNOPSIS π¦
lxc storage bucket key create [:] [flags]
No cap, that's literally the shape of it. Flags go on the end, iykyk.
πΈ DESCRIPTION πΈ
Description: create a key for a storage bucket. Your bucket needs a key, you make a key, the key goes in the bucket. Iconic, lowkey, straightforward. π
π OPTIONS π
--access-key=""β the access key. If you leave it empty, it gets auto-generated for you β no cap, the command's got you. ``--role="read-only"β the role. Your choices areadminorread-only. Default isread-only, and honestly, that's the responsible main character choice. ``--secret-key=""β the secret key π€«. Leave it empty and it's auto-generated too. ``--target=""β cluster member name. Like, which member of the cluster you're aiming at. π― ``
π§ OPTIONS INHERITED FROM PARENT COMMANDS π§
These are the hand-me-downs from the parent command, and yeah, they're still iconic:
--debug[=false]β show all the debug messages. Every single one.falseis the default.--force-local[=false]β force using the local unix socket, fr fr.-h,--help[=false]β print help. The classic.falseby default.--project=""β override the source project. ``-q,--quiet[=false]β don't show progress information. For when you want peace and quiet.falseby default.--sub-commands[=false]β use this withhelpor--helpto view the sub-commands.falseby default.-v,--verbose[=false]β show all the information messages. The opposite of quiet.falseby default.--version[=false]β print the version number.falseby default.
π EXAMPLE π
Bestie, the examples ate. Look:
lxc storage bucket key create p1 b01 k1
Create a key called k1 for the bucket b01 in the pool p1.
lxc storage bucket key create p1 b01 k1 < config.yaml
Create a key called k1 for the bucket b01 in the pool p1 using the content of config.yaml.
So the first one is just... make the key. The second one pipes config.yaml straight in as the content β the < doing its little redirect thing. Chef's kiss. π
Heads up babes: both examples use poolp1, bucketb01, keyk1. Keep it exact, don't get creative with the names, that's the assignment.
π SEE ALSO π
lxc-storage-bucket-key(1)β the parent page, go read that one too. π«Ά
π HISTORY π
22-Aug-2026 β auto generated by spf13/cobra. Not me, not you, the tool did it. π
Okay that's the whole page, bestie, you're officially educated π
β¨ β this little number was auto generated by spf13/cobra, dated Aug 2026, and it lives under the banner of LXD - Command line client(1). Go forth and create keys. ππ¦πΈ
π¦ where this page comes from
- opensuse-leap 16.0: lxd 5.21.6-bp160.1.1 Β· AGPL-3.0-only AND Apache-2.0
- opensuse-leap 16.0: lxd 5.21.6-bp160.1.1 Β· AGPL-3.0-only AND Apache-2.0
- opensuse-leap 16.0: lxd 5.21.6-bp160.1.1 Β· AGPL-3.0-only AND Apache-2.0
- opensuse-leap 16.0: lxd 5.21.6-bp160.1.1 Β· AGPL-3.0-only AND Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms