[CRIU] unclear CRIU and docker problems

Cyrill Gorcunov gorcunov at gmail.com
Tue Jun 30 01:57:39 PDT 2015


On Tue, Jun 30, 2015 at 10:45:15AM +0200, Adrian Reber wrote:
> 
> # criu check
> Warn  (mem.c:52): Can't reset 18563's dirty memory tracker (22)
> Warn  (cr-check.c:581): Dirty tracking is OFF. Memory snapshot will not work.
> Looks good.
> 
> I can checkpoint/restore/migrate processes outside of the container but
> I will try to look if and what is missing with PID namespaces.

lsmod please


More information about the CRIU mailing list