<div dir="ltr">Another update: I was intrigued by the exit code (which implies SIGPIPE?), since the docker process I was running was indeed piping:<div><br></div><div> /bin/sh -c 'i=0; while true; do echo $i; i=$(expr $i + 1); sleep 3; done'</div><div><br></div><div>I tried the same process of checkpointing in one container and restoring to another by writing to a file instead:</div><div>
<p class=""><span class=""> /bin/sh -c 'i=0; while true; do echo $i > /tmp/foo; i=$(expr $i + 1); sleep 3; done'</span></p></div>
<div class="gmail_extra">And this worked correctly! So I've narrowed it done some more, and I'll continue to look into it.</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 23, 2015 at 1: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">As a follow up, I tried manually editing the cgroup image file to swap the ID of the original container with the one I am restoring in, and the process still dies, so that probably isn't the issue.</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 23, 2015 at 1:21 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">Hey everyone, <div><br></div><div>I've gotten a bit further along in my project and run into a new issue. Right now, to make my system work, I name my docker containers and keep them around. But since they're all (essentially) identical, I'd like to just delete them and create new ones as needed. So, I'm working on checkpointing a container, and then later restoring the image files into a new container. </div><div><br></div><div>This seems to half work. Here's a dump and restore log from two separate containers (I included the args sent to criu):</div><div><br></div><div>dump: <a href="https://gist.github.com/boucher/9cc5a952a82c8f8b01b5" target="_blank">https://gist.github.com/boucher/9cc5a952a82c8f8b01b5</a><br></div><div>restore: <a href="https://gist.github.com/boucher/ffb6699353e01a09dff5" target="_blank">https://gist.github.com/boucher/ffb6699353e01a09dff5</a></div><div><br></div><div>Criu reports that the restore worked successfully, but after the restore the new container/process immediately dies (the process itself is just a simple bash script that echoes in a loop forever). No errors are printed anywhere by docker or criu that I can find. </div><div><br></div><div>The only information I have to go on right now is the exit code (141), and the logs. My hunch is that it has to do with the cgroup info in the image files, since the id of the original container (03cc978e3d29....) is making its way into the restore log as well.</div><div><br></div><div>I appreciate any suggestions. I'm going to be playing around with --cgroup-root next to see if I can make that work.</div><span><font color="#888888"><div><br></div><div>- Ross</div><div><br></div></font></span></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div></div>