1podman-container-checkpoint(1)()              podman-container-checkpoint(1)()
2
3
4

NAME

6       podman-container-checkpoint  - Checkpoints one or more running contain‐
7       ers
8
9

SYNOPSIS

11       podman container checkpoint [options] container ...
12
13

DESCRIPTION

15       Checkpoints all the processes in one or more containers.  You  may  use
16       container IDs or names as input.
17
18

OPTIONS

20   --keep, -k
21       Keep  all  temporary  log  and  statistics files created by CRIU during
22       checkpointing. These files are not deleted if checkpointing  fails  for
23       further  debugging. If checkpointing succeeds these files are theoreti‐
24       cally not needed, but if these files are needed  Podman  can  keep  the
25       files for further analysis.
26
27
28   --all, -a
29       Checkpoint all running containers.
30
31
32   --latest, -l
33       Instead of providing the container name or ID, checkpoint the last cre‐
34       ated container.
35
36
37       The latest option is not supported on the remote client.
38
39
40   --leave-running, -R
41       Leave the container running after checkpointing instead of stopping it.
42
43
44   --tcp-established
45       Checkpoint a container with established TCP connections. If the  check‐
46       point  image  contains  established  TCP  connections,  this options is
47       required during restore. Defaults to not checkpointing containers  with
48       established TCP connections.
49
50
51   --export, -e
52       Export  the checkpoint to a tar.gz file. The exported checkpoint can be
53       used to import the container on another system and thus  enabling  con‐
54       tainer  live  migration.  This  checkpoint  archive  also  includes all
55       changes to the container's root file-system, if not explicitly disabled
56       using --ignore-rootfs
57
58
59   --ignore-rootfs
60       This  only  works  in combination with --export, -e. If a checkpoint is
61       exported  to  a  tar.gz  file  it  is  possible  with   the   help   of
62       --ignore-rootfs  to  explicitly  disable  including changes to the root
63       file-system into the checkpoint archive file.
64
65
66   --ignore-volumes
67       This option must be used in combination with the --export,  -e  option.
68       When  this  option is specified, the content of volumes associated with
69       the container will not be included into the checkpoint tar.gz file.
70
71
72   --pre-checkpoint, -P
73       Dump the container's memory information  only,  leaving  the  container
74       running.  Later operations will supersede prior dumps. It only works on
75       runc 1.0-rc3 or higher.
76
77
78   --with-previous
79       Check out the container with previous criu image files in pre-dump.  It
80       only  works  without  --pre-checkpoint  or  -P.  It  only works on runc
81       1.0-rc3 or higher.
82
83

EXAMPLE

85       podman container checkpoint mywebserver
86
87
88       podman container checkpoint 860a4b23
89
90
91       podman container checkpoint -P -e pre-checkpoint.tar.gz -l
92
93
94       podman container checkpoint --with-previous -e checkpoint.tar.gz -l
95
96

SEE ALSO

98       podman(1), podman-container-restore(1)
99
100

HISTORY

102       September 2018, Originally compiled by Adrian  Reber  areber@redhat.com
103       ⟨mailto:areber@redhat.com⟩
104
105
106
107                                              podman-container-checkpoint(1)()