opensource/podman
1
0
Fork 0
mirror of https://github.com/containers/podman.git synced 2025-09-27 08:43:52 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #3443 from adrianreber/rootfs-changes-migration

Browse Source 
Include changes to the container's root file-system in the checkpoint archive
This commit is contained in:
OpenShift Merge Robot
2019-07-19 02:38:26 +02:00
committed by GitHub
parent b59abdc1b1 c70657a6d1
commit deb087d7b1
13 changed files with 276 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/podman-container-checkpoint.1.md
View File

@ -42,7 +42,15 @@ connections.
Export the checkpoint to a tar.gz file. The exported checkpoint can be used
to import the container on another system and thus enabling container live
migration.
migration. This checkpoint archive also includes all changes to the container's
root file-system, if not explicitly disabled using **--ignore-rootfs**
**--ignore-rootfs**
This only works in combination with **--export, -e**. If a checkpoint is
exported to a tar.gz file it is possible with the help of **--ignore-rootfs**
to explicitly disable including changes to the root file-system into
the checkpoint archive file.
## EXAMPLE

7
docs/podman-container-restore.1.md
View File

@ -60,6 +60,13 @@ address to the container it was using before checkpointing as each IP address ca
be used once and the restored container will have another IP address. This also means
that **--name, -n** cannot be used in combination with **--tcp-established**.
**--ignore-rootfs**
This is only available in combination with **--import, -i**. If a container is restored
from a checkpoint tar.gz file it is possible that it also contains all root file-system
changes. With **--ignore-rootfs** it is possible to explicitly disable applying these
root file-system changes to the restored container.
## EXAMPLE
podman container restore mywebserver