mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-08-23 16:57:51 +00:00
f7c8fd8a3d
runc uses CRIU to support checkpoint and restore of containers. This brings an initial checkpoint/restore implementation to podman. None of the additional runc flags are yet supported and container migration optimization (pre-copy/post-copy) is also left for the future. The current status is that it is possible to checkpoint and restore a container. I am testing on RHEL-7.x and as the combination of RHEL-7 and CRIU has seccomp troubles I have to create the container without seccomp. With the following steps I am able to checkpoint and restore a container: # podman run --security-opt="seccomp=unconfined" -d registry.fedoraproject.org/f27/httpd # curl -I 10.22.0.78:8080 HTTP/1.1 403 Forbidden # <-- this is actually a good answer # podman container checkpoint <container> # curl -I 10.22.0.78:8080 curl: (7) Failed connect to 10.22.0.78:8080; No route to host # podman container restore <container> # curl -I 10.22.0.78:8080 HTTP/1.1 403 Forbidden I am using CRIU, runc and conmon from git. All required changes for checkpoint/restore support in podman have been merged in the corresponding projects. To have the same IP address in the restored container as before checkpointing, CNI is told which IP address to use. If the saved network configuration cannot be found during restore, the container is restored with a new IP address. For CRIU to restore established TCP connections the IP address of the network namespace used for restore needs to be the same. For TCP connections in the listening state the IP address can change. During restore only one network interface with one IP address is handled correctly. Support to restore containers with more advanced network configuration will be implemented later. v2: * comment typo * print debug messages during cleanup of restore files * use createContainer() instead of createOCIContainer() * introduce helper CheckpointPath() * do not try to restore a container that is paused * use existing helper functions for cleanup * restructure code flow for better readability * do not try to restore if checkpoint/inventory.img is missing * git add checkpoint.go restore.go v3: * move checkpoint/restore under 'podman container' v4: * incorporated changes from latest reviews Signed-off-by: Adrian Reber <areber@redhat.com> |
||
|---|---|---|
| .. | ||
| docker | ||
| formats | ||
| libpodruntime | ||
| shared | ||
| varlink | ||
| attach.go | ||
| build.go | ||
| checkpoint.go | ||
| cleanup.go | ||
| commit.go | ||
| common.go | ||
| common_test.go | ||
| container.go | ||
| create.go | ||
| create_cli.go | ||
| create_cli_test.go | ||
| diff.go | ||
| exec.go | ||
| export.go | ||
| history.go | ||
| image.go | ||
| images.go | ||
| import.go | ||
| info.go | ||
| inspect.go | ||
| kill.go | ||
| load.go | ||
| login.go | ||
| logout.go | ||
| logs.go | ||
| main.go | ||
| mount.go | ||
| parse.go | ||
| pause.go | ||
| pod.go | ||
| pod_create.go | ||
| pod_inspect.go | ||
| pod_kill.go | ||
| pod_pause.go | ||
| pod_ps.go | ||
| pod_restart.go | ||
| pod_rm.go | ||
| pod_start.go | ||
| pod_stats.go | ||
| pod_stop.go | ||
| pod_top.go | ||
| pod_unpause.go | ||
| port.go | ||
| ps.go | ||
| pull.go | ||
| push.go | ||
| README.md | ||
| refresh.go | ||
| restart.go | ||
| restore.go | ||
| rm.go | ||
| rmi.go | ||
| run.go | ||
| run_test.go | ||
| runlabel.go | ||
| save.go | ||
| search.go | ||
| sigproxy.go | ||
| start.go | ||
| stats.go | ||
| stop.go | ||
| tag.go | ||
| top.go | ||
| umount.go | ||
| unpause.go | ||
| utils.go | ||
| varlink.go | ||
| varlink_dummy.go | ||
| version.go | ||
| wait.go | ||
podman - Simple debugging tool for pods and images
podman is a daemonless container runtime for managing containers, pods, and container images. It is intended as a counterpart to CRI-O, to provide low-level debugging not available through the CRI interface used by Kubernetes. It can also act as a container runtime independent of CRI-O, creating and managing its own set of containers.
Use cases
- Create containers
- Start, stop, signal, attach to, and inspect existing containers
- Run new commands in existing containers
- Push and pull images
- List and inspect existing images
- Create new images by committing changes within a container
- Create pods
- Start, stop, signal, and inspect existing pods
- Populate pods with containers