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. (This option is not available with  the  remote  Podman
35       client)
36
37
38   --leave-running, -R
39       Leave the container running after checkpointing instead of stopping it.
40
41
42   --tcp-established
43       Checkpoint  a container with established TCP connections. If the check‐
44       point image contains established TCP connections, this options  is  re‐
45       quired  during  restore.  Defaults to not checkpointing containers with
46       established TCP connections.
47
48
49   --export, -e
50       Export the checkpoint to a tar.gz file. The exported checkpoint can  be
51       used  to  import the container on another system and thus enabling con‐
52       tainer live  migration.  This  checkpoint  archive  also  includes  all
53       changes to the container's root file-system, if not explicitly disabled
54       using --ignore-rootfs
55
56
57   --ignore-rootfs
58       This only works in combination with --export, -e. If  a  checkpoint  is
59       exported  to  a  tar.gz  file  it  is  possible  with the help of --ig‐
60       nore-rootfs  to  explicitly  disable  including  changes  to  the  root
61       file-system into the checkpoint archive file.
62
63
64   --ignore-volumes
65       This  option  must be used in combination with the --export, -e option.
66       When this option is specified, the content of volumes  associated  with
67       the container will not be included into the checkpoint tar.gz file.
68
69
70   --pre-checkpoint, -P
71       Dump  the  container's  memory  information only, leaving the container
72       running. Later operations will supersede prior dumps. It only works  on
73       runc 1.0-rc3 or higher.
74
75
76   --with-previous
77       Check  out the container with previous criu image files in pre-dump. It
78       only works without --pre-checkpoint  or  -P.  It  only  works  on  runc
79       1.0-rc3 or higher.
80
81

EXAMPLE

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

SEE ALSO

96       podman(1), podman-container-restore(1)
97
98

HISTORY

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