iac.htora.dev · security templates

Home/Refreshers/Checkpoints and node memory: refresher

Checkpoints and node memory

Which nodes let you checkpoint a container or capture their memory, and the commands for each on EKS and GKE.

NodesCheckpointNode memory
EKS, Amazon Linux 2023After installing CRIUAVML through SSM
EKS, BottlerocketNoAVML from the admin container, untested
GKE, Container-Optimized OSPod snapshots, GKE Sandbox onlyAVML from a privileged pod
GKE AutopilotPod snapshots, GKE Sandbox onlyNo

Commands

Checkpoint, from the nodecurl -sk -X POST -H "Authorization: Bearer $TOKEN" https://localhost:10250/checkpoint/<ns>/<pod>/<container>
Node memory, through a pipe to S3mkfifo p; aws s3 cp - s3://<bucket>/<case>/<node>.lime < p & ./avml acquire p
Container-Optimized OS kernelgcloud storage cp gs://cos-tools/<BUILD_ID>/vmlinux .
Check the kernel bannervol -f <image> banners.Banners

Watch out

  • Grant create on nodes/checkpoint. nodes/proxy reaches exec in every container.
  • Never lower kernel lockdown to capture. It needs a reboot, which loses the memory.
  • AVML refuses /dev/stdout. Write into a named pipe.
  • Both kinds of image contain secrets in clear.
Check it worked

The image's kernel banner matches uname -r from the node, and its hash matches the one taken while streaming.

Read the full pageDownload PDF

Registry 0.23.0. Built 2026-11-17.

Made by Habibullah Tora. Source on GitHub. Code under the MIT licence, writing under CC BY 4.0.