Docker Community Forums

Share and learn in the Docker community.

Docker checkpoint create fails - active TCP connections


(Yotamhc) #1

Hi,

I’m trying to use docker checkpoint for a network application. It fails and from looking at the CRIU logs I can see the following error:

Error (criu/sk-inet.c:167): Connected TCP socket, consider using --tcp-established option

From reading the CRIU documentation, this flag should solve the problem.
I was wondering if there is a way to make docker pass this option to CRIU. Or if not, then whether I can call CRIU directly and have the same expected behavior as of calling docker checkpoint create.

I enabled the experimental option in daemon.json.

System info:
Docker version 17.12.1-ce, build 7390fc6
CRIU version 2.6
OS: Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-119-generic x86_64)

Thanks,
Yotam


(Yotamhc) #2

Adding info: I found the underlying docker-runc command that is generated by the docker checkpoint call, and added –tcp-established. It worked (criu log shows it was successful and files are in place), but the checkpoint does not appear in the docker checkpoint ls results. Can I still use this checkpoint with docker somehow (i.e., restore it)?


(Extracluster) #3

I think this will do
docker start --checkpoint checkp_name container_name
How did you get the underlying docker-runc command that is generated by the docker checkpoint??