lxc-destroy(1)

💖 NAME 💖

ok so bestie, this is lxc-destroy — section 1 of the manual, the destroy a container girlie 💅 she's the one you call when a container has gotta GO.

✨ SYNOPSIS ✨

lxc-destroy {-n name} [-f] [-s]

🦋 DESCRIPTION 🦋

lxc-destroy destroys the system object that was previously created by the lxc-create command. that's it, that's the whole vibe — it's the cleanup queen 👑 you made it with lxc-create, now you unmake it, no cap.

🎀 OPTIONS 🎀

• -f, --force — if the container is running, stop it first. and like, if you don't pass this and the container IS running? then lxc-destroy gets aborted, periodt. so basically it's the "idc just do it" flag 🫶
• -s, --snapshots — destroy the specified container including all its snapshots. all of them. every last one. iconic but ruthless 💀

🌸 COMMON OPTIONS 🌸

these ones are common to most of the lxc commands, so you'll see them everywhere, iykyk:

• -?, -h, --help — print a longer usage message than normal. the deluxe version 💖
• --usage — give the usage message
• -q, --quiet — mute on 🔇
• -P, --lxcpath=PATH — use an alternate container path. the default is /var/lib/lxc
• -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, little heads up: this option sets the priority of the events log in the alternate log file. it does not have any effect on the ERROR events log on stderr. so don't come for her when stderr is still loud 🙈

• -n, --name=NAME — use container identifier NAME. the container identifier format is an alphanumeric string
• --rcfile=FILE — specify the configuration file used to configure the virtualization and isolation functionalities for the container

and bestie, listen: this configuration file, if present, will be used even if there's already a configuration file present in the previously created container (via lxc-create). she said this one, and she meant it 💅

• --version — show the version number

---

💀 DIAGNOSTIC 💀

• The container was not found — the specified container for destruction was not found 😭 it's probable it doesn't exist and was already destroyed. you can use the lxc-ls command to list the available containers on the system — go check, she might already be gone fr fr.

🌈 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 destroy responsibly ✨💜

this little masterpiece is dated 2026-05-01 and lives under the name lxc-destroy(1) — mwah, take care, ily 🫶🎀