332
edits
Changes
Jump to navigation
Jump to search
mLine 1:
Line 1: + + + + Line 21:
Line 25: − +
no edit summary
This article describes the status of checkpoint/restore integration with [https://containerd.io/ containerd], and how to use it.
This article describes the status of checkpoint/restore integration with [https://containerd.io/ containerd], and how to use it.
One thing that may be confusing at first is the separation between a "container" and a "task" in containerd. A container is a metadata object that resources are allocated and attached to. A task is a live, running process on the system. Tasks should be deleted after each run while a container can be used, updated, and queried multiple times.
== Container Checkpoint/Restore ==
== Container Checkpoint/Restore ==
The following example shows how to run a container from an OCI image, create a checkpoint of the running container, and restore a new container from the checkpoint.
{{Note|<code>ctr</code> is unsupported debug and administrative client for interacting with the containerd daemon. The commands, options, and operations are not guaranteed to be backward compatible or stable from release to release of the containerd project.}}
{{Note|<code>ctr</code> is unsupported debug and administrative client for interacting with the containerd daemon. The commands, options, and operations are not guaranteed to be backward compatible or stable from release to release of the containerd project.}}
ctr images ls 'name==checkpoint/redis:cr-1'
ctr images ls 'name==checkpoint/redis:cr-1'
Restore container from checkpoint
Restore container from checkpoint with new ID (redis-debug)
ctr c restore --rw --live redis-debug checkpoint/redis:cr-1
ctr c restore --rw --live redis-debug checkpoint/redis:cr-1