<div dir="ltr">I don't entirely follow. Is there any way to change this behavior? When I print the eth0 IP from my C program before restoring the IP is what I expect, and then after restoring its changed, and that change seems to be system wide.</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 28, 2015 at 1:06 AM, Pavel Emelyanov <span dir="ltr"><<a href="mailto:xemul@parallels.com" target="_blank">xemul@parallels.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 04/28/2015 03:06 AM, Ross Boucher wrote:<br>
> If you restore an image that had dumped tcp connections, does CRIU try to change<br>
> the ip address of the host if there's a mismatch?<br>
<br>
</span>Nope :)<br>
<span class=""><br>
> In my experiment of spinning up a new docker container with an image from a different<br>
> container, the new container gets a new ip address, but when I exec into the new<br>
> container and ask it's IP, it seems to be set to the old IP address.<br>
<br>
</span>That's because criu saves ip addresses of the net namespace it dumps, so on<br>
restore old addresses would be set inside net namespace.<br>
<br>
-- Pavle<br>
</blockquote></div><br></div>