[CRIU] Dumping lxc container failed - CRIU 1.6

[Tycho Andersen]

On Thu, Jun 25, 2015 at 03:27:46PM +0300, Pavel Emelyanov wrote:
> On 06/25/2015 03:14 PM, Thouraya TH wrote:
> > No, i have used -s option so it is not RUNNING.
> 
> What does this option mean for lxc? And what if you don't use one
> and just lxc-checkpoint the container instead?

-s just corresponds to --leave-running in criu (although it is
effectively required right now, since most things will modify at least
the syslog if you don't also have a hook to snapshot the fs as well).

Tycho

> > Kind regards.
> > 
> > 2015-06-25 12:01 GMT+01:00 Pavel Emelyanov <xemul at parallels.com <mailto:xemul at parallels.com>>:
> > 
> >     On 06/25/2015 01:15 PM, Thouraya TH wrote:
> >     > Hi all,
> >     >
> >     > May be, cloning containeris the source of the problem...
> >     >
> >     > /Does it happen always? What if you try to dump this container again without restart?
> >     > /
> >     > Did you mean:
> >     >
> >     > lxc-checkpoint -s -D /tmp/dire -n worker1
> >     > lxc-start -n worker1  ( i have to restart all process needed inside the container)
> >     > lxc-checkpoint -s -D /tmp/dire1 -n worker1
> > 
> >     Yes, but without the lxc-start in between (the container remains running after
> >     first dump, doesn't it?)
> > 
> > 
> 
> _______________________________________________
> CRIU mailing list
> CRIU at openvz.org
> https://lists.openvz.org/mailman/listinfo/criu