github.com/containers/podman/v2@v2.2.2-0.20210501105131-c1e07d070c4c/docs/source/markdown/podman-container-restore.1.md (about)

     1  % podman-container-restore(1)
     2  
     3  ## NAME
     4  podman\-container\-restore - Restores one or more containers from a checkpoint
     5  
     6  ## SYNOPSIS
     7  **podman container restore** [*options*] *container* ...
     8  
     9  ## DESCRIPTION
    10  Restores a container from a checkpoint. You may use container IDs or names as input.
    11  
    12  ## OPTIONS
    13  #### **--keep**, **-k**
    14  
    15  Keep all temporary log and statistics files created by CRIU during
    16  checkpointing as well as restoring. These files are not deleted if restoring
    17  fails for further debugging. If restoring succeeds these files are
    18  theoretically not needed, but if these files are needed Podman can keep the
    19  files for further analysis. This includes the checkpoint directory with all
    20  files created during checkpointing. The size required by the checkpoint
    21  directory is roughly the same as the amount of memory required by the
    22  processes in the checkpointed container.
    23  
    24  Without the **-k**, **--keep** option the checkpoint will be consumed and cannot be used
    25  again.
    26  
    27  #### **--all**, **-a**
    28  
    29  Restore all checkpointed containers.
    30  
    31  #### **--latest**, **-l**
    32  
    33  Instead of providing the container name or ID, restore the last created container.
    34  
    35  The latest option is not supported on the remote client.
    36  
    37  #### **--tcp-established**
    38  
    39  Restore a container with established TCP connections. If the checkpoint image
    40  contains established TCP connections, this option is required during restore.
    41  If the checkpoint image does not contain established TCP connections this
    42  option is ignored. Defaults to not restoring containers with established TCP
    43  connections.
    44  
    45  #### **--import**, **-i**
    46  
    47  Import a checkpoint tar.gz file, which was exported by Podman. This can be used
    48  to import a checkpointed container from another host. Do not specify a *container*
    49  argument when using this option.
    50  
    51  #### **--name**, **-n**
    52  
    53  This is only available in combination with **--import, -i**. If a container is restored
    54  from a checkpoint tar.gz file it is possible to rename it with **--name, -n**. This
    55  way it is possible to restore a container from a checkpoint multiple times with different
    56  names.
    57  
    58  If the **--name, -n** option is used, Podman will not attempt to assign the same IP
    59  address to the container it was using before checkpointing as each IP address can only
    60  be used once and the restored container will have another IP address. This also means
    61  that **--name, -n** cannot be used in combination with **--tcp-established**.
    62  
    63  #### **--ignore-rootfs**
    64  
    65  This is only available in combination with **--import, -i**. If a container is restored
    66  from a checkpoint tar.gz file it is possible that it also contains all root file-system
    67  changes. With **--ignore-rootfs** it is possible to explicitly disable applying these
    68  root file-system changes to the restored container.
    69  
    70  #### **--ignore-static-ip**
    71  
    72  If the container was started with **--ip** the restored container also tries to use that
    73  IP address and restore fails if that IP address is already in use. This can happen, if
    74  a container is restored multiple times from an exported checkpoint with **--name, -n**.
    75  
    76  Using **--ignore-static-ip** tells Podman to ignore the IP address if it was configured
    77  with **--ip** during container creation.
    78  
    79  #### **--ignore-static-mac**
    80  
    81  If the container was started with **--mac-address** the restored container also
    82  tries to use that MAC address and restore fails if that MAC address is already
    83  in use. This can happen, if a container is restored multiple times from an
    84  exported checkpoint with **--name, -n**.
    85  
    86  Using **--ignore-static-mac** tells Podman to ignore the MAC address if it was
    87  configured with **--mac-address** during container creation.
    88  ## EXAMPLE
    89  
    90  podman container restore mywebserver
    91  
    92  podman container restore 860a4b23
    93  
    94  ## SEE ALSO
    95  podman(1), podman-container-checkpoint(1)
    96  
    97  ## HISTORY
    98  September 2018, Originally compiled by Adrian Reber <areber@redhat.com>