A very good interview with one of the CRIU devs on FLOSS Weekly.<p><a href="https://twit.tv/show/floss-weekly/334" rel="nofollow">https://twit.tv/show/floss-weekly/334</a><p><a href="http://www.youtube.com/watch?v=w5ftqjOrpfA" rel="nofollow">http://www.youtube.com/watch?v=w5ftqjOrpfA</a><p>Some of this stuff is crazy. Moving processes is cool, but faking TCP/IP state between containers to basically transfer a TCP/IP stream from one machine to the other with client service devices noticing? INSANE.<p>I am a Linux enthusiast and very novice *nix sysadmin. It is worth the listen, even if you are not way into containerization, because what they have accomplished is impressive.
* Docker fork with CRIU support Known Issues:<p>Currently, networking is broken in this PR.<p>Although it's implemented at the libcontainer level, the method used no longer works since the introduction of libnetwork.<p>There are likely several networking related issues to work out, like:<p>- ensuring IPs are reserved across daemon restarts<p>- ensuring port maps are reserved<p>- deciding how to deal with network resources in the "new container" model
I've made a talk about this a couple of months ago for a local meetup in argentina: <a href="https://www.youtube.com/watch?v=0ZKE5nJFDJ0" rel="nofollow">https://www.youtube.com/watch?v=0ZKE5nJFDJ0</a><p>I also would like to share something I did for the Docker global hackday: <a href="https://github.com/marcosnils/cmt" rel="nofollow">https://github.com/marcosnils/cmt</a>.
Btw, the container migration will be supported by runC natively: <a href="https://github.com/opencontainers/runc/tree/master/libcontainer#checkpoint--restore" rel="nofollow">https://github.com/opencontainers/runc/tree/master/libcontai...</a>
What are the posible practical uses of this technology ?
I was thinking that could be useful to get "snapshots" of a system when a fatal exception is raised, then download the files and practice a forensic analysis. Maybe it's too much overhead ? other uses?