runc-checkpoint(8)

✨ NAME ✨

runc-checkpoint β€” checkpoint a running container πŸ’–

Like, it takes a running container and freezes its whole vibe into a save file. Bestie, it's a screenshot but for a process tree. Iconic.


πŸŽ€ SYNOPSIS πŸŽ€

runc checkpoint [option ...] container-id

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so the checkpoint command saves the state of the running container instance β€” with a little help from the criu(8) tool 🧚 β€” so you can restore it later. That's the whole plot. Save now, resurrect later. No cap.


πŸ’… OPTIONS πŸ’…

  • --image-path path β€” sets the path where the criu image files get saved. Default is ./checkpoint. Put your little memories somewhere cute.
  • --work-path path β€” sets the path for saving criu work files and logs. The default is to just reuse the image files directory. Sharing is caring fr fr.
  • --parent-path path β€” sets the path for previous criu image files, in pre-dump. Yes queen, referencing the older pics.
  • --leave-running β€” leave the process running after checkpointing. It's giving "you can look but you can't touch" πŸ’…
  • --tcp-established β€” allow checkpoint/restore of established TCP connections. See the criu --tcp-establised option (https://criu.org/CLI/opt/--tcp-established). (That spelling is the manpage's, not mine, don't come for me πŸ’€)
  • --tcp-skip-in-flight β€” skip in-flight TCP connections. See the criu --skip-in-flight option (https://criu.org/CLI/opt/--skip-in-flight). The ones mid-flight? Not invited. πŸ›«
  • --link-remap β€” allows you to link unlinked files back when possible. See the criu --link-remap option (https://criu.org/CLI/opt/--link-remap).
  • --ext-unix-sk β€” allow checkpoint/restore of external unix sockets. See the criu --ext-unix-sk option (https://criu.org/CLI/opt/--ext-unix-sk).
  • --shell-job β€” allow checkpoint/restore of shell jobs. Your lil background & gremlins get to come along 🫢
  • --lazy-pages β€” use the lazy migration mechanism. See the criu --lazy-pages option (https://criu.org/CLI/opt/--lazy-pages). She's lazy but she's efficient, main character energy.
  • --status-fd fd β€” pass a file descriptor fd to criu. Once the lazy-pages server is ready, criu writes \0 (a zero byte) to that fd. Used together with --lazy-pages. So it pings you when it's ready, like a good bestie.
  • --page-server IP-address:port β€” start a page server at the specified IP-address and port. This is used together with criu lazy-pages. See criu lazy migration (https://criu.org/Lazy_migration).
  • --file-locks β€” allow checkpoint/restore of file locks. See the criu --file-locks option (https://criu.org/CLI/opt/--file-locks). The locks are coming with you, periodt.
  • --pre-dump β€” do a pre-dump, i.e. dump the container's memory information only, leaving the container running. See criu iterative migration (https://criu.org/Iterative_migration). A lil sneak peek dump, a trailer if you will 🎬
  • --manage-cgroups-mode soft|full|strict|ignore β€” cgroups mode. Default is soft. See the criu --manage-cgroups option (https://criu.org/CLI/opt/--manage-cgroups). Pick your fighter.
  • --empty-ns namespace β€” checkpoint a namespace, but don't save its properties. See the criu --empty-ns option (https://criu.org/CLI/opt/--empty-ns). Empty on purpose. Not empty by accident. Big difference πŸ’…
  • --auto-dedup β€” enable auto deduplication of memory images. See the criu --auto-dedup option (https://criu.org/CLI/opt/--auto-dedup). Declutter queen 🌸

πŸ‘‘ SEE ALSO πŸ‘‘

criu(8), runc-restore(8), runc(8), criu(8).

(Yes, criu(8) is listed twice. Twice the love, twice the icon status. Not a typo on my end, I promise 🫢)


And that's the page, bestie! This one lives in the System Manager's Manual, and the footer is just runc-checkpoint(8) all on her lonesome β€” no date, no version, she's mysterious like that βœ¨πŸ’– Go save a container's whole soul. Slay.

πŸ“¦ where this page comes from