[CRIU] CRIU restored Docker IP address

[Ross Boucher]

Hi Rohit,

Can you clarify a couple of things? Where did you get your binary for
checkpoint/restore in docker, what version is it? And, are you just doing:
docker checkpoint <id>; docker restore <id>; or something more complicated?

-Ross

On Thu, Oct 22, 2015 at 6:42 PM Rohit Upadhyaya <rohitju at cmu.edu> wrote:

> Hi,
>
> I searched a bit on the CRIU archives and could find only one thread with
> a similar problem:
> https://lists.openvz.org/pipermail/criu/2015-April/020192.html .How would
> one use netns to connect a client to a restored container? I'm basically
> trying to reconnect to a server running on a restored Docker container and
> am kind of stuck on the IP issue.
>
> Thanks,
> Rohit
>
> On Thu, Oct 22, 2015 at 10:04 AM, Rohit Upadhyaya <rohitju at cmu.edu> wrote:
>
>> Hi,
>>
>> I have been playing around with CRIU with Docker and am facing a problem
>> with the way a new IP address is assigned to a resumed container. I have a
>> TCP server running on the container and on restore a new IP address is
>> assigned and my client is unable to talk to the server (even on the new
>> IP). Looking at the restore log I find that the restore process restores
>> the socket descriptors with the old IP address. Is there any way to force
>> the restored container to run on the old IP?
>>
>>
>>
> _______________________________________________
> CRIU mailing list
> CRIU at openvz.org
> https://lists.openvz.org/mailman/listinfo/criu
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20151022/f0f081f7/attachment.html>