Checkpoint and restore Docker containers with CRIU

Re:Checkpoint and restore Docker containers with CRIU by alfonsodev on Tuesday September 22, 2015 @12:30PM (#10259675)

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?

[ Parent | on HN ]

Re:Checkpoint and restore Docker containers with CRIU by vezzy-fnord on Tuesday September 22, 2015 @12:58PM (#10259898)

Fast startup, obviating the need for any readiness notification (the point of execution can be guaranteed to correspond to readiness), time-travel debugging, process migration, rollback/rollforward of execution state, orthogonal persistence, etc.

The original motivation for checkpointing, IIRC, was not to lose the state of really long (days, weeks...) computations. But it goes much further.

[ Parent | on HN ]

Re:Checkpoint and restore Docker containers with CRIU by laurencerowe on Tuesday September 22, 2015 @07:09PM (#10262323)

Being able to use AWS spot instances for long running batch processes would be great. We have some bioinformatics analysis jobs that take days to complete and this could cut their cost by ~80%.

[ Parent | on HN ]

Re:Checkpoint and restore Docker containers with CRIU by marcosnils on Wednesday September 23, 2015 @07:10PM (#10268886)

I'm interested about your use case, can you ping me at @marcosnils?

Thx!.

[ Parent | on HN ]

Re:Checkpoint and restore Docker containers with CRIU by batbomb on Tuesday September 22, 2015 @01:09PM (#10259988)

Batch processing with preemptable jobs.

[ Parent | on HN ]

Re:Checkpoint and restore Docker containers with CRIU by alfonsodev on Tuesday September 22, 2015 @12:32PM (#10259690)

or perhaps implement snapshots in a similar way than 'virtualbox' does ?

[ Parent | on HN ]