summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAdrian Reber <areber@redhat.com>2018-09-19 17:11:17 +0000
committerAdrian Reber <adrian@lisas.de>2018-10-03 21:41:40 +0200
commit5bafafc7eb31152b12627a1bf07657013ee01027 (patch)
tree96cc549d3410f87bbb8291f470b0fc857fc515ee
parente2b639a32fa2386c53d8a77fe18543bb054a95dd (diff)
downloadpodman-5bafafc7eb31152b12627a1bf07657013ee01027.tar.gz
podman-5bafafc7eb31152b12627a1bf07657013ee01027.tar.bz2
podman-5bafafc7eb31152b12627a1bf07657013ee01027.zip
tutorial: add checkpoint/restore to tutorial
Signed-off-by: Adrian Reber <areber@redhat.com>
-rw-r--r--docs/tutorials/podman_tutorial.md22
1 files changed, 22 insertions, 0 deletions
diff --git a/docs/tutorials/podman_tutorial.md b/docs/tutorials/podman_tutorial.md
index a866b8eed..152d65a59 100644
--- a/docs/tutorials/podman_tutorial.md
+++ b/docs/tutorials/podman_tutorial.md
@@ -157,6 +157,28 @@ $ sudo podman top <container_id>
101 31889 31873 0 09:21 ? 00:00:00 nginx: worker process
```
+### Checkpointing the container
+Checkpointing a container stops the container while writing the state of all processes in the container to disk.
+With this a container can later be restored and continue running at exactly the same point in time as the
+checkpoint. This capability requires CRIU 3.11 or later installed on the system.
+To checkpoint the container use:
+```console
+$ sudo podman container checkpoint <container_id>
+```
+
+### Restoring the container
+Restoring a container is only possible for a previously checkpointed container. The restored container will
+continue to run at exactly the same point in time it was checkpointed.
+To restore the container use:
+```console
+$ sudo podman container restore <container_id>
+```
+
+After being restored, the container will answer requests again as it did before checkpointing.
+```console
+# curl http://<IP_address>:8080
+```
+
### Stopping the container
To stop the httpd container:
```console