[CRIU] alternate implementation of --ext-unix-sk

Tycho Andersen tycho.andersen at canonical.com
Mon Nov 9 16:00:23 PST 2015


Hi all,

in 79fd764ae6c4eabcc12da0159e4ad96b02431df0 and
http://criu.org/External_UNIX_socket#What_to_do_with_socketpair.28.29-s.3F

an implementation of --ext-unix-sk is described that you pass the
inode of the external socket. One way to find this inode is to look
for a specific path in /proc/net/unix inside the container's netns.

Is there any reason we can't just pass --ext-unix-sk=/foo/bar and have
every socket connected to this be dumpable and restorable (by being
reconnected as described on the wiki)? This would be less work (and
more intiutive, I think) for most than passing the inode number, but I
might be missing something.

Thanks,

Tycho


More information about the CRIU mailing list