1podman-container-restore(1)() podman-container-restore(1)()
2
3
4
6 podman-container-restore - Restores one or more containers from a
7 checkpoint
8
9
11 podman container restore [options] container ...
12
13
15 Restores a container from a checkpoint. You may use container IDs or
16 names as input.
17
18
20 --keep, -k
21 Keep all temporary log and statistics files created by CRIU during
22 checkpointing as well as restoring. These files are not deleted if
23 restoring fails for further debugging. If restoring succeeds these
24 files are theoretically not needed, but if these files are needed Pod‐
25 man can keep the files for further analysis. This includes the check‐
26 point directory with all files created during checkpointing. The size
27 required by the checkpoint directory is roughly the same as the amount
28 of memory required by the processes in the checkpointed container.
29
30
31 Without the -k, --keep option the checkpoint will be consumed and can‐
32 not be used again.
33
34
35 --all, -a
36 Restore all checkpointed containers.
37
38
39 --latest, -l
40 Instead of providing the container name or ID, restore the last created
41 container. (This option is not available with the remote Podman client)
42
43
44 --tcp-established
45 Restore a container with established TCP connections. If the checkpoint
46 image contains established TCP connections, this option is required
47 during restore. If the checkpoint image does not contain established
48 TCP connections this option is ignored. Defaults to not restoring con‐
49 tainers with established TCP connections.
50
51
52 --import, -i
53 Import a checkpoint tar.gz file, which was exported by Podman. This can
54 be used to import a checkpointed container from another host. Do not
55 specify a container argument when using this option.
56
57
58 --import-previous
59 Import a pre-checkpoint tar.gz file which was exported by Podman. This
60 option must be used with -i or --import. It only works on runc 1.0-rc3
61 or higher.
62
63
64 --name, -n
65 This is only available in combination with --import, -i. If a container
66 is restored from a checkpoint tar.gz file it is possible to rename it
67 with --name, -n. This way it is possible to restore a container from a
68 checkpoint multiple times with different names.
69
70
71 If the --name, -n option is used, Podman will not attempt to assign the
72 same IP address to the container it was using before checkpointing as
73 each IP address can only be used once and the restored container will
74 have another IP address. This also means that --name, -n cannot be used
75 in combination with --tcp-established.
76
77
78 --ignore-rootfs
79 This is only available in combination with --import, -i. If a container
80 is restored from a checkpoint tar.gz file it is possible that it also
81 contains all root file-system changes. With --ignore-rootfs it is pos‐
82 sible to explicitly disable applying these root file-system changes to
83 the restored container.
84
85
86 --ignore-static-ip
87 If the container was started with --ip the restored container also
88 tries to use that IP address and restore fails if that IP address is
89 already in use. This can happen, if a container is restored multiple
90 times from an exported checkpoint with --name, -n.
91
92
93 Using --ignore-static-ip tells Podman to ignore the IP address if it
94 was configured with --ip during container creation.
95
96
97 --ignore-static-mac
98 If the container was started with --mac-address the restored container
99 also tries to use that MAC address and restore fails if that MAC ad‐
100 dress is already in use. This can happen, if a container is restored
101 multiple times from an exported checkpoint with --name, -n.
102
103
104 Using --ignore-static-mac tells Podman to ignore the MAC address if it
105 was configured with --mac-address during container creation.
106
107
108 --ignore-volumes
109 This option must be used in combination with the --import, -i option.
110 When restoring containers from a checkpoint tar.gz file with this op‐
111 tion, the content of associated volumes will not be restored.
112
113
115 podman container restore mywebserver
116
117
118 podman container restore 860a4b23
119
120
121 podman container restore --import-previous pre-checkpoint.tar.gz --im‐
122 port checkpoint.tar.gz
123
124
126 podman(1), podman-container-checkpoint(1)
127
128
130 September 2018, Originally compiled by Adrian Reber areber@redhat.com
131 ⟨mailto:areber@redhat.com⟩
132
133
134
135 podman-container-restore(1)()