288ccc4c84
When migrating a container with associated volumes, the content of these volumes should be made available on the destination machine. This patch enables container checkpoint/restore with named volumes by including the content of volumes in checkpoint file. On restore, volumes associated with container are created and their content is restored. The --ignore-volumes option is introduced to disable this feature. Example: # podman container checkpoint --export checkpoint.tar.gz <container> The content of all volumes associated with the container are included in `checkpoint.tar.gz` # podman container checkpoint --export checkpoint.tar.gz --ignore-volumes <container> The content of volumes is not included in `checkpoint.tar.gz`. This is useful, for example, when the checkpoint/restore is performed on the same machine. # podman container restore --import checkpoint.tar.gz The associated volumes will be created and their content will be restored. Podman will exit with an error if volumes with the same name already exist on the system or the content of volumes is not included in checkpoint.tar.gz # podman container restore --ignore-volumes --import checkpoint.tar.gz Volumes associated with container must already exist. Podman will not create them or restore their content. Signed-off-by: Radostin Stoyanov <rstoyanov@fedoraproject.org>
2.3 KiB
% podman-container-checkpoint(1)
NAME
podman-container-checkpoint - Checkpoints one or more running containers
SYNOPSIS
podman container checkpoint [options] container ...
DESCRIPTION
Checkpoints all the processes in one or more containers. You may use container IDs or names as input.
OPTIONS
--keep, -k
Keep all temporary log and statistics files created by CRIU during checkpointing. These files are not deleted if checkpointing fails for further debugging. If checkpointing succeeds these files are theoretically not needed, but if these files are needed Podman can keep the files for further analysis.
--all, -a
Checkpoint all running containers.
--latest, -l
Instead of providing the container name or ID, checkpoint the last created container.
The latest option is not supported on the remote client.
--leave-running, -R
Leave the container running after checkpointing instead of stopping it.
--tcp-established
Checkpoint a container with established TCP connections. If the checkpoint image contains established TCP connections, this options is required during restore. Defaults to not checkpointing containers with established TCP connections.
--export, -e
Export the checkpoint to a tar.gz file. The exported checkpoint can be used to import the container on another system and thus enabling container live migration. This checkpoint archive also includes all changes to the container's root file-system, if not explicitly disabled using --ignore-rootfs
--ignore-rootfs
This only works in combination with --export, -e. If a checkpoint is exported to a tar.gz file it is possible with the help of --ignore-rootfs to explicitly disable including changes to the root file-system into the checkpoint archive file.
--ignore-volumes
This option must be used in combination with the --export, -e option. When this option is specified, the content of volumes associated with the container will not be included into the checkpoint tar.gz file.
EXAMPLE
podman container checkpoint mywebserver
podman container checkpoint 860a4b23
SEE ALSO
podman(1), podman-container-restore(1)
HISTORY
September 2018, Originally compiled by Adrian Reber areber@redhat.com