Replies: 2 comments 1 reply
-
I've been experimenting with how to implement this on AL2023. The version of containerd that is included in the EKS optimized AMI (1.7) does not expose CheckpointContainer unless it is patched and rebuilt. I assume that this is also an issue on Bottlerocket. When I tried upgrading to a newer version of containerd (2.1.4) I started getting shim errors. |
Beta Was this translation helpful? Give feedback.
-
Hi, we have a similar issue open asking for support for CRIU at #3803 Bottlerocket currently doesn't support checkpointing. The error I received is below for reference:
I had to create a service account on my cluster to get this working with
We recently merged containerd-2.1 in bottlerocket-os/bottlerocket-core-kit#621 which opens up a path to enable this. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Is it possible to checkpoint a container running on EKS? If the latest version of EKS variant supports containerd 2.0, it should be theoretically possible. In order to checkpoint a container you need to run cURL -k POST http://localhost:10250/checkpoint/{namespace}/{pod}/{container} from the node. I assume you could do this from a control and/or admin container so long as you passed in the appropriate cert/key. My initial attempts at this failed on Auto Mode node which I know is a slightly different variant than the EKS variant. I basically want to know if this will work on BR and Auto Mode. See https://seifrajhi.github.io/blog/k8s-criu-container-checkpointing/ for reference.
Beta Was this translation helpful? Give feedback.
All reactions