<div dir="ltr"><div><div>Hi,<br><br>I searched a bit on the CRIU archives and could find only one thread with a similar problem: <a href="https://lists.openvz.org/pipermail/criu/2015-April/020192.html">https://lists.openvz.org/pipermail/criu/2015-April/020192.html</a> .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.<br><br></div>Thanks,<br></div>Rohit<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 22, 2015 at 10:04 AM, Rohit Upadhyaya <span dir="ltr"><<a href="mailto:rohitju@cmu.edu" target="_blank">rohitju@cmu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi,<br><br></div>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?<br><br><br></div>
</blockquote></div><br></div>