LXC.CONFIG.GET(1)

πŸ“¦
version 5.21.6 Β· 3 versions
, in opensuse-leap 16.0

✨ LXC.CONFIG.GET(1) β€” bestie edition ✨

okay so real quick, before we even start: this is the man page for lxc-config-get, and it lives under the whole LXD - Command line client(1) umbrella πŸ’… like, that's the family it belongs to. Anyway. Let's get into it πŸŽ€


🌸 NAME 🌸

lxc-config-get β€” grab the values for instance or server configuration keys 🫢

Like, you point at a key and it hands you the value. That's the whole gig. Slay.


⭐ SYNOPSIS ⭐

lxc config get [:][]  [flags]

not me showing you the synopsis with those little empty brackets 😭 that's literally how it's written in the source, I'm not gaslighting you β€” the square brackets are just sitting there with nothing inside. anyway, that's the shape of the command, and [flags] means the options below are up for grabs ✨


πŸ¦‹ DESCRIPTION πŸ¦‹

Description: get values for instance or server configuration keys πŸ’–

fr fr that's it. you want to know what a config key is set to? this is the little icon that does it. no cap.


πŸ‘‘ OPTIONS πŸ‘‘

the good stuff. the main character options. let's go 🌈

  • -e, --expanded[=false] β€” access the expanded configuration πŸ‘€ (default is false, so you have to actually ask for it)
  • -p, --property[=false] β€” get the key as an instance property instead πŸ’… (also defaults to false)
  • --target="" β€” the cluster member name 🧚 defaults to "", so like, no member picked unless you say so
lowkey the little backticks in the source for --target are a whole formatting moment, but the info is exactly this: cluster member name, default empty string 🫢

πŸ“ OPTIONS INHERITED FROM PARENT COMMANDS πŸ“

these aren't even hers, she's just borrowing them from the parent command and honestly? iconic 🌟

  • --debug[=false] β€” show all debug messages πŸ”₯ (default false)
  • --force-local[=false] β€” force using the local unix socket πŸ”Œ (default false)
  • -h, --help[=false] β€” print help 😌 (default false)
  • --project="" β€” override the source project πŸŽ€ default is "", so it's empty until you fill it in
  • -q, --quiet[=false] β€” don't show progress information 🀫 (default false)
  • --sub-commands[=false] β€” use with help or --help to view sub-commands 🧭 (default false)
  • -v, --verbose[=false] β€” show all information messages πŸ“£ (default false)
  • --version[=false] β€” print version number 🏷️ (default false)
also yes, --project has the same little backtick artifact situation going on in the source. the fact is: it overrides the source project, default "". we move πŸ’œ

πŸ’œ SEE ALSO πŸ’œ

  • lxc-config(1) β€” go say hi to the parent, she's lovely 🫢

🧚 HISTORY 🧚

  • 22-Aug-2026 β€” auto generated by spf13/cobra πŸ€–βœ¨

bestie reminder: everything here is auto-generated, so if something looks a lil phoned-in, that's why 😭 the facts are still facts though β€” every flag, every default, every empty string, all accounted for πŸ’―

and that's the page!! mwah πŸ’‹ this has been LXD - Command line client(1), dated Aug 2026, auto generated by spf13/cobra β€” periodt, go read some config keys πŸ‘‘πŸŒΈ

πŸ“¦ where this page comes from