[CRIU] Dumping lxc container failed - CRIU 1.6

[Pavel Emelyanov]

On 06/25/2015 05:51 PM, Tycho Andersen wrote:
> 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).

If it's the --leave-running, why after checkpoint containers is not RUNNING
(according to Thouraya)? O_o

But, anyway, my question was -- what if we try to checkpoint the container
several times in a row, would the "bad socket" appear all the time?

-- Pavel