Checkpoint and restore Docker containers with CRIU
blog.circleci.com
Checkpoint and restore Docker containers with CRIU
1–10 of 15 posts
Re: Checkpoint and restore Docker containers with CRIU
#2* Docker fork with CRIU support Known Issues:
Currently, networking is broken in this PR.
Although it's implemented at the libcontainer level, the method used no longer works since the introduction of libnetwork.
There are likely several networking related issues to work out, like:
- ensuring IPs are reserved across daemon restarts
- ensuring port maps are reserved
- deciding how to deal with network resources in the "new container" model
Re: Checkpoint and restore Docker containers with CRIU
#3A very good interview with one of the CRIU devs on FLOSS Weekly.
https://twit.tv/show/floss-weekly/334
http://www.youtube.com/watch?v=w5ftqjOrpfA
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.
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.
Re: Checkpoint and restore Docker containers with CRIU
#4A very good interview with one of the CRIU devs on FLOSS Weekly. https://twit.tv/show/floss-weekly/334 http://www.youtube.com/watch?v=w5ftqjOrpfA 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. I am a Linux enthusiast and very novice *nix sysadmin. It is w…
EROS and KeyKOS accomplished the same OS-wide some 25 years ago, though they were also built on a completely different process model. Grasshopper [1] was another system from the same time period built around orthogonal persistence.
Bolting checkpointing on top of a monolithic Unix is harder, though doable. DragonFly BSD has had a rather elegant and simple mechanism called sys_checkpoint(2) since 2003, but is still limited to single-threaded programs.
Re: Checkpoint and restore Docker containers with CRIU
#5I've made a talk about this a couple of months ago for a local meetup in argentina: https://www.youtube.com/watch?v=0ZKE5nJFDJ0
I also would like to share something I did for the Docker global hackday: https://github.com/marcosnils/cmt.
Re: Checkpoint and restore Docker containers with CRIU
#6Btw, the container migration will be supported by runC natively: https://github.com/opencontainers/runc/tree/master/libcontai...
Re: Checkpoint and restore Docker containers with CRIU
#7Btw, the container migration will be supported by runC natively: https://github.com/opencontainers/runc/tree/master/libcontai...
Re: Checkpoint and restore Docker containers with CRIU
#8Thank you for sharing. This blogpost is gold for Docker Continuous integration: http://cloudacademy.com/blog/continuous-integration-docker/
Re: Checkpoint and restore Docker containers with CRIU
#9What 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?
Re: Checkpoint and restore Docker containers with CRIU
#10What 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?
or perhaps implement snapshots in a similar way than 'virtualbox' does ?