lxc-info(1)

πŸ’… lxc-info(1) β€” the manual page, but make it group chat

ok so bestie, welcome to lxc-info, your new fave little detective for containers ✨ The manual name is literally right there in the title (lxc-info(1)) β€” cute, we love a self-referential queen πŸ’–

🌸 NAME 🌸

lxc-info β€” query information about a container πŸ‘‘

✨ SYNOPSIS ✨

lxc-info {-n name} [-c KEY] [-s] [-p] [-i] [-S] [-H]

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so here's the vibe: lxc-info queries and shows information about a container. That's it, that's the whole job, and honestly? She ate. πŸ’…

πŸŽ€ OPTIONS πŸŽ€

  • -c, --config KEY β€” prints a configuration key from the container. Lowkey obsessed with this one: you can give this option multiple times to print out multiple key = value pairs, so go off, stack them 🫢
  • -s, --state β€” just print the container's state. nothing else, just the state, keep it brief bestie 🀫
  • -p, --pid β€” just print the container's pid. the main character's process ID, iconic πŸ”₯
  • -i, --ips β€” just print the container's IP addresses. all of them, address reveal era 🌈
  • -S, --stats β€” just print the container's statistics. BUT β€” heads up, bestie, this is the fine-print moment 🚨 for performance reasons the kernel does not account kernel memory use unless a kernel memory limit is set. If a limit is not set, lxc-info will display kernel memory use as 0. So if you're squinting at a big fat zero, that's why, no cap. A limit can be set by specifying
lxc.cgroup.memory.kmem.limit_in_bytes = number

in your container configuration file, see lxc.conf(5). slay πŸ’œ

  • -H, --no-humanize β€” print the container's statistics in raw, non-humanized form. the default is to print statistics in humanized form. so like, -H is the "give me the actual numbers, no vibes" flag 😌

🌟 COMMON OPTIONS 🌟

these options are common to most of lxc commands, iykyk πŸ’«

  • -?, -h, --help β€” print a longer usage message than normal. the deluxe edition πŸ“–
  • --usage β€” give the usage message. short and sweet ✨
  • -q, --quiet β€” mute on πŸ”‡
  • -P, --lxcpath=PATH β€” use an alternate container path. the default is /var/lib/lxc. path relocation, we love to see it πŸŽ€
  • -o, --logfile=FILE β€” output to an alternate log FILE. the default is no log πŸ«₯
  • -l, --logpriority=LEVEL β€” set log priority to LEVEL. the default log priority is ERROR. Possible values are: FATAL, ALERT, CRIT, WARN, ERROR, NOTICE, INFO, DEBUG, TRACE.
ngl, read this part twice bestie πŸ‘€ β€” this option is setting the priority of the events log in the alternate log file. It do not have effect on the ERROR events log on stderr. so don't come for me when stderr is still yelling 😭
  • -n, --name=NAME β€” use container identifier NAME. the container identifier format is an alphanumeric string πŸ”€
  • --rcfile=FILE β€” specify the configuration file to configure the virtualization and isolation functionalities for the container.
important: this configuration file, if present, will be used even if there is already a configuration file present in the previously created container (via lxc-create). she overrides, periodt πŸ’…
  • --version β€” show the version number. say hi to the version πŸ–οΈ

🌈 EXAMPLES 🌈

  • lxc-info -n foo Show information for foo. the classic, the starter pack πŸ“
  • lxc-info -n 'ubuntu.*' Show information for all containers whose name starts with ubuntu. yes the wildcard, yes it's giving main character energy πŸ‘‘
  • lxc-info -n foo -c lxc.net.0.veth.pair prints the veth pair name of foo. look at her, getting all specific πŸ”

πŸ’œ SEE ALSO πŸ’œ

lxc(7), lxc-create(1), lxc-copy(1), lxc-destroy(1), lxc-start(1), lxc-stop(1), lxc-execute(1), lxc-console(1), lxc-monitor(1), lxc-wait(1), lxc-cgroup(1), lxc-ls(1), lxc-info(1), lxc-freeze(1), lxc-unfreeze(1), lxc-attach(1), lxc.conf(5)


okay that's the whole page bestie, go forth and query some containers πŸ’–βœ¨πŸŽ€πŸ¦‹

this little masterpiece is from the lxc-info(1) fam, dated 2026-05-01 β€” take care of her, she's iconic πŸ‘‘πŸ’…

πŸ“¦ where this page comes from