Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for container restore from a checkpoint in Kubernetes #10093

Open
rst0git opened this issue Apr 19, 2024 · 0 comments
Open

Add support for container restore from a checkpoint in Kubernetes #10093

rst0git opened this issue Apr 19, 2024 · 0 comments

Comments

@rst0git
Copy link
Contributor

rst0git commented Apr 19, 2024

containerd provides native support for checkpoint/restore using checkpoint images. The more recently introduced functionality that connects the existing checkpoint functions to the CRI ContainerCheckpoint RPC allows to export the 1) CRIU data, 2) rootfs diff, and 3) spec from the checkpoint image into a tar archive. This tar archive has format similar to the one used by CRI-O. However, since containerd has native support for checkpoint images and CRI-O does not, it is unclear how to enable the restore functionality.

There are two approaches that we could use to enable container restore with containerd in Kubernetes:

  1. We can use a tool such as checkpointctl to create a checkpoint image in the format currently used by containerd, or
  2. Modify containerd to support restore with the checkpoint image format used by CRI-O.

@adrianreber @estesp Do you have any advice or recommendations on which approach might be more suitable?

cc: @liunan-ms @viktoriaas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant