1podman-container-restore(1)() podman-container-restore(1)()
2
6 podman-container-restore - Restores one or more containers from a
7 checkpoint
8
11 podman container restore [options] container ...
12
15 Restores a container from a checkpoint. You may use container IDs or
16 names as input.
17
20 --keep, -k
21 Keep all temporary log and statistics files created by CRIU during
24 checkpointing as well as restoring. These files are not deleted if
25 restoring fails for further debugging. If restoring succeeds these
26 files are theoretically not needed, but if these files are needed Pod‐
27 man can keep the files for further analysis. This includes the check‐
28 point directory with all files created during checkpointing. The size
29 required by the checkpoint directory is roughly the same as the amount
30 of memory required by the processes in the checkpointed container.
31 Without the -k, --keep option the checkpoint will be consumed and can‐
34 not be used again.
35 --all, -a
38 Restore all checkpointed containers.
41 --latest, -l
44 Instead of providing the container name or ID, restore the last created
47 container.
48 The latest option is not supported on the remote client.
51 --tcp-established
54 Restore a container with established TCP connections. If the checkpoint
57 image contains established TCP connections, this option is required
58 during restore. If the checkpoint image does not contain established
59 TCP connections this option is ignored. Defaults to not restoring con‐
60 tainers with established TCP connections.
61 --import, -i
64 Import a checkpoint tar.gz file, which was exported by Podman. This can
67 be used to import a checkpointed container from another host. Do not
68 specify a container argument when using this option.
69 --name, -n
72 This is only available in combination with --import, -i. If a container
75 is restored from a checkpoint tar.gz file it is possible to rename it
76 with --name, -n. This way it is possible to restore a container from a
77 checkpoint multiple times with different names.
78 If the --name, -n option is used, Podman will not attempt to assign the
81 same IP address to the container it was using before checkpointing as
82 each IP address can only be used once and the restored container will
83 have another IP address. This also means that --name, -n cannot be used
84 in combination with --tcp-established.
85 --ignore-rootfs
88 This is only available in combination with --import, -i. If a container
91 is restored from a checkpoint tar.gz file it is possible that it also
92 contains all root file-system changes. With --ignore-rootfs it is pos‐
93 sible to explicitly disable applying these root file-system changes to
94 the restored container.
95 --ignore-static-ip
98 If the container was started with --ip the restored container also
101 tries to use that IP address and restore fails if that IP address is
102 already in use. This can happen, if a container is restored multiple
103 times from an exported checkpoint with --name, -n.
104 Using --ignore-static-ip tells Podman to ignore the IP address if it
107 was configured with --ip during container creation.
108 --ignore-static-mac
111 If the container was started with --mac-address the restored container
114 also tries to use that MAC address and restore fails if that MAC
115 address is already in use. This can happen, if a container is restored
116 multiple times from an exported checkpoint with --name, -n.
117 Using --ignore-static-mac tells Podman to ignore the MAC address if it
120 was configured with --mac-address during container creation.
121
124 podman container restore mywebserver
125 podman container restore 860a4b23
128
131 podman(1), podman-container-checkpoint(1)
132
135 September 2018, Originally compiled by Adrian Reber areber@redhat.com
136 ⟨mailto:areber@redhat.com⟩
137 podman-container-restore(1)()