1podman-container-restore(1) General Commands Manualpodman-container-restore(1)
2
3
4

NAME

6       podman-container-restore - Restores one or more running containers
7
8

SYNOPSIS

10       podman container restore [options] container ...
11
12

DESCRIPTION

14       Restores a container from a checkpoint. You may use container IDs or
15       names as input.
16
17

OPTIONS

19       --keep, -k
20
21
22       Keep all temporary log and statistics files created by CRIU during
23       checkpointing as well as restoring. These files are not deleted if
24       restoring fails for further debugging. If restoring succeeds these
25       files are theoretically not needed, but if these files are needed
26       Podman can keep the files for further analysis. This includes the
27       checkpoint directory with all files created during checkpointing. The
28       size required by the checkpoint directory is roughly the same as the
29       amount of memory required by the processes in the checkpointed
30       container.
31
32
33       Without the -k, --keep option the checkpoint will be consumed and
34       cannot be used again.
35
36
37       --all, -a
38
39
40       Restore all checkpointed containers.
41
42
43       --latest, -l
44
45
46       Instead of providing the container name or ID, restore the last created
47       container.
48
49
50       The latest option is not supported on the remote client.
51
52
53       --tcp-established
54
55
56       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
60       containers with established TCP connections.
61
62
63       --import, -i
64
65
66       Import a checkpoint tar.gz file, which was exported by Podman. This can
67       be used to import a checkpointed container from another host. It is not
68       necessary to specify a container when restoring from an exported
69       checkpoint.
70
71
72       --name, -n
73
74
75       This is only available in combination with --import, -i. If a container
76       is restored from a checkpoint tar.gz file it is possible to rename it
77       with --name, -n. This way it is possible to restore a container from a
78       checkpoint multiple times with different names.
79
80
81       If the --name, -n option is used, Podman will not attempt to assign the
82       same IP address to the container it was using before checkpointing as
83       each IP address can only be used once and the restored container will
84       have another IP address. This also means that --name, -n cannot be used
85       in combination with --tcp-established.
86
87

EXAMPLE

89       podman container restore mywebserver
90
91
92       podman container restore 860a4b23
93
94

SEE ALSO

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

HISTORY

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