You'll have to exec as privileged. I'm not sure if that feature is currently in the cli but it is in the remote API. <br><br>You want something more like: ip added add NEWIP dev eth0<br><div class="gmail_quote"><div dir="ltr">On Tue, Nov 10, 2015 at 10:27 AM Rohit Upadhyaya <<a href="mailto:rohitju@cmu.edu">rohitju@cmu.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Thanks Ross, with the branch you mentioned I was able to checkpoint, restore and even connect to a container. But the restore and connect works only if the IP assigned by Docker is the same on both the checkpoint host and restore host. This usually means that I have to start the containers in order so that the Docker daemon assigns the same IP in both places. I tried to exec (privileged) into the machine and run 'ip addr dev eth0' but this just gives me a 'RTNETLINK: Operation not permitted' error. Is there anything else I could do?<br><br></div>Thanks,<br></div>Rohit<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 23, 2015 at 12:40 PM, 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">Ah I was on the wrong branch, my apologies. I am now able to see the checkpoint/restore commands and will test out connecting to a restored container which hopefully works. Thanks for the help!<br></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 23, 2015 at 12:11 PM, Ross Boucher <span dir="ltr"><<a href="mailto:rboucher@gmail.com" target="_blank">rboucher@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Are you sure you are on the right branch? I don't think that sounds right. Sorry I'm on my phone I can look more closely in a bit. <br><div><div><div class="gmail_quote"><div dir="ltr">On Fri, Oct 23, 2015 at 12:06 PM Rohit Upadhyaya <<a href="mailto:rohitju@cmu.edu" target="_blank">rohitju@cmu.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Yup I see the "# WARNING! DOCKER_EXPERIMENTAL is set: building experimental features" message at the end. I'm using the binary bundles/1.7.0-dev/binary/docker-1.7.0-dev since the VERSION file in the huikang branch is 1.7. <br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 23, 2015 at 10:46 AM, Ross Boucher <span dir="ltr"><<a href="mailto:rboucher@gmail.com" target="_blank">rboucher@gmail.com</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">In your build log, towards the end, you should see this:<div><div><br></div><div># WARNING! DOCKER_EXPERIMENTAL is set: building experimental features</div></div><div><br></div><div>Are you sure that you're then using the binary in bundles/1.9.0-dev/binary/docker-1.9.0-dev?</div></div><div><div><br><div class="gmail_quote"><div dir="ltr">On Fri, Oct 23, 2015 at 10:45 AM Ross Boucher <<a href="mailto:rboucher@gmail.com" target="_blank">rboucher@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I build by just running this command:<div><br></div><div>DOCKER_EXPERIMENTAL=1 make binary<br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Oct 23, 2015 at 10:43 AM Rohit Upadhyaya <<a href="mailto:rohitju@cmu.edu" target="_blank">rohitju@cmu.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Thanks, Ross. Would you happen to know how I would build docker with experimental features? I tried setting the DOCKER_EXPERIMENTAL=1 environment variable but the generated binary does not seem to have the checkpoint and restore commands.</p>
<div style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">So, networking is most likely broken in that build. If you try building from this branch, you might have better luck:<div><a href="https://github.com/huikang/docker/tree/fix-restore-network-cr-combined-1006" target="_blank">https://github.com/huikang/docker/tree/fix-restore-network-cr-combined-1006</a><br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Oct 22, 2015 at 6:50 PM Rohit Upadhyaya <<a href="mailto:rohitju@cmu.edu" target="_blank">rohitju@cmu.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hi Ross,<br><br></div>I am using Docker version 1.9.0 from the vagrant box here: <a href="https://vagrantcloud.com/kimh/boxes/criu" target="_blank">https://vagrantcloud.com/kimh/boxes/criu</a> and I followed the instructions here: <a href="http://blog.circleci.com/checkpoint-and-restore-docker-container-with-criu/" target="_blank">http://blog.circleci.com/checkpoint-and-restore-docker-container-with-criu/</a>. I am doing nothing more than running `docker checkpoint <id>` (with a TCP server running) followed by a `docker restore <id>`.<br><br></div>Thanks,<br></div>Rohit<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 22, 2015 at 6:45 PM, Ross Boucher <span dir="ltr"><<a href="mailto:rboucher@gmail.com" target="_blank">rboucher@gmail.com</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">Hi Rohit,<div><br></div><div>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?</div><div><br></div><div>-Ross</div></div><br><div class="gmail_quote"><span><div dir="ltr">On Thu, Oct 22, 2015 at 6:42 PM Rohit Upadhyaya <<a href="mailto:rohitju@cmu.edu" target="_blank">rohitju@cmu.edu</a>> wrote:<br></div></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><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" target="_blank">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></span>
_______________________________________________<br>
CRIU mailing list<br>
<a href="mailto:CRIU@openvz.org" target="_blank">CRIU@openvz.org</a><br>
<a href="https://lists.openvz.org/mailman/listinfo/criu" rel="noreferrer" target="_blank">https://lists.openvz.org/mailman/listinfo/criu</a><br>
</blockquote></div>
</blockquote></div><br></div>
</blockquote></div>
</div>
</blockquote></div></blockquote></div>
</div></div></blockquote></div><br></div>
</blockquote></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</blockquote></div>