Docker - Revision history

Radostin at 13:06, 25 July 2025

2025-07-25T13:06:09Z

Radostin at 13:01, 25 July 2025

2025-07-25T13:01:45Z

Radostin at 09:06, 12 October 2021

2021-10-12T09:06:53Z

Radostin: /* TTY */ Update info about support for checkpointing of an interactive container

2019-01-25T07:22:57Z

TTY: Update info about support for checkpointing of an interactive container

Radostin: Add more info about passing additional options

2019-01-25T07:16:12Z

Add more info about passing additional options

Kir: rewording

2017-03-31T22:21:46Z

rewording

Kir: /* Integration Status */ integrated, thus removing

2017-03-31T22:16:03Z

Integration Status: integrated, thus removing

Kir: /* External Checkpoint Restore */ slight rewording

2017-03-31T22:15:07Z

External Checkpoint Restore: slight rewording

Kir: refer to installation

2017-03-31T22:13:26Z

refer to installation

Kir: /* Docker Experimental */ minor rewording

2017-03-31T22:12:02Z

Docker Experimental: minor rewording

@@ Line 1: / Line 1: @@
 This article describes the status of CRIU integration with Docker, and how to use it.
-{{Note|We are working in close collaboration with the Podman developers to implement checkpoint/restore support and recommend using Podman as an alternative to Docker.}}
+{{Note|We are working in close collaboration with the Podman developers to implement checkpoint/restore support and recommend using [[Podman]] as an alternative to Docker.}}
 == Docker Experimental ==

← Older revision		Revision as of 13:01, 25 July 2025
Line 1:		Line 1:
	This article describes the status of CRIU integration with Docker, and how to use it.		This article describes the status of CRIU integration with Docker, and how to use it.
		+
		+	{{Note\|We are working in close collaboration with the Podman developers to implement checkpoint/restore support and recommend using Podman as an alternative to Docker.}}

	== Docker Experimental ==		== Docker Experimental ==

@@ Line 21: / Line 21: @@
 First, we create container:
-  $ docker run -d --name looper --security-opt seccomp:unconfined busybox  \
+  $ docker run -d --name looper busybox /bin/sh -c 'i=0; while true; do echo $i; i=$(expr $i + 1); sleep 1; done'
 You can verify the container is running by printings its logs:

@@ Line 103: / Line 103: @@
 === TTY ===
-Checkpointing an interactive container is currently not supported.
+Checkpointing an interactive container is supported by CRIU, runc and containerd, but not yet enabled in Docker.
 === Seccomp ===

← Older revision		Revision as of 07:16, 25 January 2019
Line 59:		Line 59:

	You should be able to print the logs from <code>looper-clone</code> and see that they start from wherever the logs of <code>looper</code> end.		You should be able to print the logs from <code>looper-clone</code> and see that they start from wherever the logs of <code>looper</code> end.
		+
		+	=== Passing additional options ===
		+
		+	[[Configuration files]] can be used to set additional CRIU options when performing checkpoint/restore of Docker containers. These options should be added in the file <code>/etc/criu/runc.conf</code> (in order to '''overwrite''' the ones set by runc/Docker). Note that the options stored in <code>~/.criu/default.conf</code> or <code>/etc/criu/default.conf</code> will be '''overwritten''' by the ones set via [[RPC]] by Docker.
		+
		+	For example, in order to checkpoint and restore a container with established TCP connections CRIU requires the <code>--tcp-established</code> option to be set. However, this option is set to false by default and it is currently not possible to change this behaviour via the command-line interface of Docker. This feature can be enabled by adding <code>tcp-established</code> in the file <code>/etc/criu/runc.conf</code>. Note that for this functionality to work, the version of [[https://github.com/opencontainers/runc runc]] must be recent enough to have the commit [[https://github.com/opencontainers/runc/commit/e157963054e1be28bcd6612f15df1ea561c62571 e157963]] applied.
		+
		+	An alternative solution is to use [https://podman.io/ Podman] which has support to specify <code>--tcp-established</code> on the command-line.

	=== Synopsis ===		=== Synopsis ===

@@ Line 1: / Line 1: @@
-This HOWTO page describes how to checkpoint and restore a Docker container.
+This article describes the status of CRIU integration with Docker, and how to use it.
 == Docker Experimental ==
-Checkpoint & Restore is now available in the ''experimental'' runtime mode for Docker. It is available since Docker 1.13, so every later version (like Docker 17.03) has it.
+Naturally, Docker wants to manage the full lifecycle of processes running inside its containers, so CRIU should be run by Docker (rather than separately).
 To enable experimental features (incl. CRIU), you need to do something like this:
@@ Line 14: / Line 11: @@
   systemctl restart docker
-=== Dependencies ===
+In addition to having a recent version of Docker, you need '''CRIU''' 2.0 or later installed on your system (see [[Installation]] for more info).
 === checkpoint ===

@@ Line 93: / Line 93: @@
        --help                    Print usage
    -i, --interactive             Attach container's STDIN
 == Compatibility Notes ==

@@ Line 148: / Line 148: @@
 * {{torvalds.git|e4a0d3e720}} by Pavel Emelyanov
-== External Checkpoint Restore ==
+== External checkpoint/restore ==
-{{Note| External C/R was done as proof-of-concept.  Its use is highly discouraged.}}
+Although it's not recommended, you can also learn more about using CRIU without integrating with Docker. See [[Docker External]] for more info.

@@ Line 16: / Line 16: @@
 === Dependencies ===
-In addition to installing version 1.13+ of Docker, you need '''CRIU''' 2.0 or later installed on your system. You also need some shared libraries on your system. The most likely things you'll need to install are '''libprotobuf-c''' and '''libnl-3'''. Here's an output of <code>ldd</code> on my system:
+In addition to installing version 1.13+ of Docker, you need '''CRIU''' 2.0 or later installed on your system (see [[Installation]] for more info).
 === checkpoint ===

@@ Line 7: / Line 7: @@
 == Docker Experimental ==
-Checkpoint & Restore is now available in the ''experimental'' runtime mode for Docker. It is avaiable in Docker 1.13, Docker 17.03 and later version.
+Checkpoint & Restore is now available in the ''experimental'' runtime mode for Docker. It is available since Docker 1.13, so every later version (like Docker 17.03) has it.
 To enable experimental features (incl. CRIU), you need to do something like this:
@@ Line 16: / Line 16: @@
 === Dependencies ===
-In addition to installing version 1.13 of Docker, you need '''CRIU''' installed on your system, with at least version 2.0. You also need some shared libraries on your system. The most likely things you'll need to install are '''libprotobuf-c''' and '''libnl-3'''. Here's an output of <code>ldd</code> on my system:
+In addition to installing version 1.13+ of Docker, you need '''CRIU''' 2.0 or later installed on your system. You also need some shared libraries on your system. The most likely things you'll need to install are '''libprotobuf-c''' and '''libnl-3'''. Here's an output of <code>ldd</code> on my system:
   $ ldd `which criu`
@@ Line 75: / Line 75: @@
 You should be able to print the logs from <code>looper-clone</code> and see that they start from wherever the logs of <code>looper</code> end.
-=== usage ===
+=== Synopsis ===
 Checkpoint