Restore network connectivity after container restore

[SaiedKazemi]

This is a work-in-progress implementation of restoring network connectivty after container restore. Its main purpose is for testing and starting a conversation for a production-quality implementation.

Signed-off-by: Saied Kazemi [email protected]

[hixichen]

hi , doest this means we will get a 'Broken pipe error'. I faced a issue that: docker run -d -p xx:xx --name server server #run as a server , bind and listening to some port.

after docker checkpoint and restore .

I can not connect to the server anymore.

sock.sendall(data) File "/usr/lib/python2.7/socket.py", line 228, in meth return getattr(self._sock,name)(*args) socket.error: [Errno 32] Broken pipe

thanks

[SaiedKazemi]

Please use Ross Boucher's docker-checkpoint-restore branch for checkpoint restore.

[hixichen]

thank you!

I found this https://github.com/boucher/docker/pull/19

docker version: Docker version 1.9.0-dev, build 59c375a, experimental get from here: https://github.com/boucher/docker/releases/tag/v1.9.0-experimental-cr.1

CRIU vesion: 2.2

After applied the --net=host option, I found the process numbers has difference.

without option , docker will create two process.

root 23376 0.1 1.5 121968 15784 ? Sl 22:35 0:00 _ docker-proxy -proto tcp -host-ip 0.0.0.0 -host- root 23394 23.3 4.2 412488 42836 ? Ssl 22:35 0:01 _ ./myapp

I guess maybe it happened because the FIFO between two processes was not handled very well. I will try to find more information.