[CRIU] Checkpointing with empty_ns and open tcp connection

Ross Boucher rboucher at gmail.com
Mon Mar 7 09:34:50 PST 2016


I'm building from master as well. Talking with Andrey this morning though,
it seems that the most likely issue is restoring an active connection but
the IP address in the container has changed.

On Mon, Mar 7, 2016 at 10:22 AM Saied Kazemi <saied at google.com> wrote:

> Ross,
>
> Yes, I've been able to restore TCP connections for the Nginx video
> streaming demo but if I keep checkpointing and restoring it will eventually
> fail due to too many file descriptors.  I think there's an FD leak
> somewhere.
>
> Which Docker and CRIU versions are you using?  Since Andrey's patch for
> --empty-ns has been merged, I am building CRIU from head.
>
> --Saied
>
>
> On Mon, Mar 7, 2016 at 8:01 AM, Andrew Vagin <avagin at virtuozzo.com> wrote:
>
>> On Sat, Mar 05, 2016 at 02:52:42PM +0000, Ross Boucher wrote:
>> > I'm trying to get my application running on top of the new experimental
>> docker
>> > networking support (with empty_ns), and running into some problems.
>> >
>> > https://gist.github.com/boucher/6156b4e3a57aa9c25bcd
>> >
>> > I believe the issue is the existence of an open connection. But I think
>> Saied
>> > mentioned he was able to get that working? Any ideas?
>>
>> Which repo do you use? I will try to look at this on my host.
>>
>> >
>> > -Ross
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20160307/a1719086/attachment-0001.html>


More information about the CRIU mailing list