*CHECKPOINTCTL-INSPECT*(1)
π 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: EnabledCRIU 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 forcheckpointctl 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:treeorjson(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
- fedora 43: checkpointctl 1:1.7.0-2.fc43 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND MIT AND MPL-2.0
- fedora 44: checkpointctl 1:1.7.0-2.fc44 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND MIT AND MPL-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms