1podman-container-checkpoint(1G)eneral Commands Manupaoldman-container-checkpoint(1)
2
3
4
6 podman-container-checkpoint - Checkpoints one or more running
7 containers
8
9
11 podman container checkpoint [options] container ...
12
13
15 Checkpoints all the processes in one or more containers. You may use
16 container IDs or names as input.
17
18
20 --keep, -k
21
22
23 Keep all temporary log and statistics files created by CRIU during
24 checkpointing. These files are not deleted if checkpointing fails for
25 further debugging. If checkpointing succeeds these files are
26 theoretically not needed, but if these files are needed Podman can keep
27 the files for further analysis.
28
29
30 --all, -a
31
32
33 Checkpoint all running containers.
34
35
36 --latest, -l
37
38
39 Instead of providing the container name or ID, checkpoint the last
40 created container.
41
42
43 The latest option is not supported on the remote client.
44
45
46 --leave-running, -R
47
48
49 Leave the container running after checkpointing instead of stopping it.
50
51
52 --tcp-established
53
54
55 Checkpoint a container with established TCP connections. If the
56 checkpoint image contains established TCP connections, this options is
57 required during restore. Defaults to not checkpointing containers with
58 established TCP connections.
59
60
61 --export, -e
62
63
64 Export the checkpoint to a tar.gz file. The exported checkpoint can be
65 used to import the container on another system and thus enabling
66 container live migration.
67
68
70 podman container checkpoint mywebserver
71
72
73 podman container checkpoint 860a4b23
74
75
77 podman(1), podman-container-restore(1)
78
79
81 September 2018, Originally compiled by Adrian Reber ⟨areber@redhat.com⟩
82
83
84
85 podman-container-checkpoint(1)