lxc-checkpoint(1)
π lxc-checkpoint(1) β the bestie's guide to freezing ur container mid-vibe π
okay so this is the lxc-checkpoint(1) manual page, and honestly? it's giving "save your whole container's soul to a folder and bring it back later" energy. let's get into it β¨
πΈ NAME πΈ
lxc-checkpoint β checkpoint a container π (like, literally snapshot its whole self)
π¦ SYNOPSIS π¦
lxc-checkpoint {-n name} {-D PATH} [-r] [-s] [-v] [-d] [-F]
β¨ DESCRIPTION β¨
lxc-checkpoint checkpoints and restores containers. that's the whole vibe. dump it, bring it back, slay π
π₯ OPTIONS π₯
-r,--restoreβ restores the checkpoint for the container instead of dumping it. so like, instead of saving, you're loading. this option is incompatible with-sβ pick a lane bestie π«Ά-D PATH,--checkpoint-dir=PATHβ the directory where the checkpoint metadata gets dumped. that's where all the goods live π-s,--stopβ optionally stop the container after dumping. this option is incompatible with-rβ again, no mixing π«-v,--verboseβ enables verbose criu logging. if u wanna see everything, this is ur moment π-d,--daemonβ restores the container in the background (and yes, this is the default). only available when you provide-rπ-F,--foregroundβ restores the container in the foreground. only available when you provide-rβοΈ
π COMMON OPTIONS π
these ones are common to most of the lxc commands β so like, the shared delulu of the whole lxc family fr fr
-?,-h,--helpβ prints a longer usage message than normal π--usageβ gives the usage message-q,--quietβ mute on π-P,--lxcpath=PATHβ uses an alternate container path. the default is/var/lib/lxcπ-o,--logfile=FILEβ outputs to an alternate logFILE. the default is no log π-l,--logpriority=LEVELβ sets log priority toLEVEL. the default log priority isERROR. possible values are:FATAL,ALERT,CRIT,WARN,ERROR,NOTICE,INFO,DEBUG,TRACE
heads up bestie: this option sets the priority of the events log in the alternate log file. it does not have effect on the ERROR events log on stderr. iykyk π
-n,--name=NAMEβ uses container identifierNAME. the container identifier format is an alphanumeric string π€--rcfile=FILEβ specifies the configuration file to configure the virtualization and isolation functionalities for the container
if this configuration file is present, it will be used even if there's already a configuration file present in the previously created container (via lxc-create). so yeah, it overrides. periodt π
--versionβ shows the version number π·οΈ
π EXAMPLES π
lxc-checkpoint -n foo -D /tmp/checkpoint
checkpoints the container foo into the directory /tmp/checkpoint π
lxc-checkpoint -r -n foo -D /tmp/checkpoint
restores the checkpoint from the directory /tmp/checkpoint π¦
π 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, no cap π this edition of lxc-checkpoint(1) is dated 2026-05-01 and it's from the lxc-checkpoint(1) manual, so like... go forth and checkpoint responsibly, bestie ππ
π¦ where this page comes from
- alpine 3.24: lxc-doc 7.0.0-r0 Β· LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms