diff options
| author | Adrian Reber <areber@redhat.com> | 2018-11-20 15:34:15 +0000 |
|---|---|---|
| committer | Adrian Reber <adrian@lisas.de> | 2018-11-20 17:25:44 +0100 |
| commit | b0572d622974837c2221ed1f01a2ab982f078370 (patch) | |
| tree | 1c4ad4bb26973210546639cbd4f86b12d8754270 /vendor/gopkg.in/yaml.v2/writerc.go | |
| parent | ff47a4c2d5485fc49f937f3ce0c4e2fd6bdb1956 (diff) | |
| download | podman-b0572d622974837c2221ed1f01a2ab982f078370.tar.gz podman-b0572d622974837c2221ed1f01a2ab982f078370.tar.bz2 podman-b0572d622974837c2221ed1f01a2ab982f078370.zip | |
Added option to keep containers running after checkpointing
CRIU supports to leave processes running after checkpointing:
-R|--leave-running leave tasks in running state after checkpoint
runc also support to leave containers running after checkpointing:
--leave-running leave the process running after checkpointing
With this commit the support to leave a container running after
checkpointing is brought to Podman:
--leave-running, -R leave the container running after writing checkpoint to disk
Now it is possible to checkpoint a container at some point in time
without stopping the container. This can be used to rollback the
container to an early state:
$ podman run --tmpfs /tmp --name podman-criu-test -d docker://docker.io/yovfiatbeb/podman-criu-test
$ curl 10.88.64.253:8080/examples/servlets/servlet/HelloWorldExample
3
$ podman container checkpoint -R -l
$ curl 10.88.64.253:8080/examples/servlets/servlet/HelloWorldExample
4
$ curl 10.88.64.253:8080/examples/servlets/servlet/HelloWorldExample
5
$ podman stop -l
$ podman container restore -l
$ curl 10.88.64.253:8080/examples/servlets/servlet/HelloWorldExample
4
So after checkpointing the container kept running and was stopped after
some time. Restoring this container will restore the state right at the
checkpoint.
Signed-off-by: Adrian Reber <areber@redhat.com>
Diffstat (limited to 'vendor/gopkg.in/yaml.v2/writerc.go')
0 files changed, 0 insertions, 0 deletions