lxc-freeze(1)

💜 lxc-freeze — bestie's guide to pausing a whole container

okay so hi 🙋‍♀️ you're reading lxc-freeze(1), the manual page for the lxc-freeze command, and honestly? it's a whole mood. let's get into it ✨

---

🎀 SYNOPSIS

lxc-freeze {-n name}

that's it. that's the whole vibe. one flag, one job 💅

---

🌸 DESCRIPTION

so lxc-freeze freezes all the processes running inside the container. like, every single one. they just… stop. mid-thought. 🧊

and they stay blocked — no cap — until someone explicitly thaws them with the lxc-unfreeze command. that's the only thing that un-pauses them, so don't think they'll just wake up on their own 🙈

ngl this command is genuinely iconic for batch managers who need to schedule a group of processes. like, freeze the whole group, do your thing, thaw them later. it's giving "main character time management" ⏰👑

---

✨ COMMON OPTIONS ✨

these are the options that are common to most of the lxc commands, so you'll see these cuties again 🫶

• -?, -h, --help — prints a longer usage message than the normal one. more words, more love 💖
• --usage — gives you the usage message. that's it, that's the whole thing 🎀
• -q, --quiet — mute on 🔇 (yes, the manpage literally says "mute on", we love a minimalist queen)
• -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 🌈

⚠️ heads up bestie: this option is setting the priority of the events log in the alternate log file. it does not have an effect on the ERROR events log on stderr. so don't come for me 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 to configure the virtualization and isolation functionalities for the container 📜

and listen: 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). so it's the override of overrides, periodt 👑

• --version — show the version number 🔢

---

🦋 DIAGNOSTIC

• the container was not found — the specified container was not created before with the lxc-create command 😭 like, she doesn't exist. you can't freeze a vibe that was never created, bestie.

---

👑 SEE ALSO

go read these next, i'm obsessed with all of them fr fr:

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)

(yes, lxc-freeze(1) is listed in its own SEE ALSO. self-love, we stan 💖)

---

🌟 sign-off

that's the whole page, bestie! this gem is dated 2026-05-01 and it's the lxc-freeze(1) page from the lxc suite — go freeze something responsibly, and remember: you can't thaw what you never froze 🧊💜 bye slay 🫶✨