[CRIU] about checkpointing lxc container

[Pavel Emelyanov]

On 10/11/2013 12:16 AM, Xinyang Ge wrote:
>> This is something we call "external resource" -- an object, that links
>> container with the outer world (typically with the host). By default CRIU
>> should only dump containers without such things, but sometimes we have to
>> manually specify exceptions to that rule.
>>
>> The terminal you're having problem with is such -- we should somehow explain
>> to CRIU, that this terminal is "external" to make CRIU dump only one half
>> of it and on restore get one from lxc container setup machinery.
> 
> OK. Looks like this is specific to the linux container. And it's
> difficult to handle such cases in a general way :(
> 
> By the way, is there any way to let the CRIU tolerate some undumpable resources?

Yes, but they are added case-by-case. E.g. we have special keys for unix
sockets, that are externally connected, for TCP sockets, for sessions, for
file locks and for veth network devices.

>> Hope this explanation helps :)
> 
> Yes, it does!! Thank you so much!
> 
> Xinyang
> 


Thanks,
Pavel