*CHECKPOINTCTL-INSPECT*(1)

πŸ“¦
version 1.7.0 Β· 6 versions
, in fedora 43, fedora 44

πŸ’– CHECKPOINTCTL-INSPECT πŸ’–

okay bestie, buckle up β€” this is checkpointctl-inspect(1) from the CHECKPOINTCTL manual, and it's literally the tool that spills all the low-level tea about a container checkpoint. no cap. 🫢


✨ NAME ✨

checkpointctl-inspect β€” display low-level information about a container checkpoint

like, ALL the down-and-dirty details, not just the vibes. πŸ”


🌸 SYNOPSIS 🌸

checkpointctl inspect [OPTION]... FILE

that's it. that's the whole summoning ritual. one FILE, as many [OPTION]s as your heart desires. πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

So the whole point is inspecting container checkpoint archives, right? iconic behavior. But here's the thing β€” if you wanna read command lines and environment variables, you need memory pages in the archive. no pages, no tea. 😭

CRIU LZ4-compressed pages get decoded automatically for you (you're welcome πŸ’–), and that needs checkpoint/inventory.img to be there. keep that in mind.

By default the output tells you one of two things:

  • CRIU compression: Enabled
  • CRIU compression: Disabled

And if you go the JSON route, the output includes the boolean field criu_compression. this setting is describing CRIU memory page compression, and it's independent of archive compression β€” two separate things, don't get it twisted. πŸ’€

Now, archives with no checkpoint/inventory.img? Those get reported as compression disabled, for compatibility with older checkpoints. nostalgia-core. And if the inventory metadata is invalid? boom, you get an error. periodt.

Also on the menu:

  • Container created β€” this is literally the container creation time.
  • Checkpoint data size β€” the combined size of files under checkpoint/, which includes memory images AND CRIU metadata.

In JSON output these values show up in created and checkpoint_size.total_size. write that down. πŸ“


πŸŽ€ OPTIONS πŸŽ€

  • -h, --help β€” show help for checkpointctl inspect (when you need a little hand-holding, we've all been there πŸ₯Ί)
  • --all β€” show all information about container checkpoints. all of it. the full meal. πŸ‘‘
  • --files β€” display the open file descriptors for processes in the container checkpoint
  • --format=FORMAT β€” specify the output format: tree or json (default "tree")
  • --metadata β€” show metadata about the container
  • --mounts β€” display an overview of mounts used in the container checkpoint
  • -p, --pid=PID β€” display the process tree of a specific PID
  • --ps-tree β€” display an overview of processes in the container checkpoint
  • --ps-tree-cmd β€” display an overview of processes in the container checkpoint with full command line arguments (the receipts πŸ“œ)
  • --ps-tree-env β€” display an overview of processes in the container checkpoint with their environment variables
  • --sockets β€” display the open sockets for processes in the container checkpoint
  • --stats β€” display checkpoint statistics (numbers!! we love numbers ✨)

πŸ‘€ SEE ALSO πŸ‘€

checkpointctl(1) β€” the main character, honestly


πŸ’œ AUTHOR πŸ’œ

The CRIU team β€” absolute legends, we stan 🫢


bestie reminder: this whole thing is checkpointctl manual material, dated 2026-10-19. go inspect something gorgeous, slay, and remember β€” the vibes change, the flags never do. πŸ’…βœ¨πŸŒˆ
πŸ“¦ where this page comes from