<div dir="ltr">Here's the output same procedure without the restore-sibling option:<div><a href="https://gist.githubusercontent.com/boucher/b18593b9da2782d17e95/raw/strace.txt">https://gist.githubusercontent.com/boucher/b18593b9da2782d17e95/raw/strace.txt</a><br></div><div><br></div><div>It's rather long. I'm not really sure how to read the strace output.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 23, 2015 at 11:39 PM, 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 06/24/2015 01:42 AM, Ross Boucher wrote:<br>
> If I run strace on the docker daemon, criu fails to restore with a different error:<br>
><br>
> <a href="https://gist.github.com/boucher/bef6e944ae700526a979" rel="noreferrer" target="_blank">https://gist.github.com/boucher/bef6e944ae700526a979</a><br>
> (I included both the restore log and the strace)<br>
><br>
> Without strace, I get the same fd already in use error.<br>
<br>
</span>Hm... The new error is because criu tries to PTRACE_SEIZE the init to do the<br>
--restore-sibling restore and can't do it since strace is already there.<br>
<br>
Can you (for experiment only) patch out the --restore-sibling option from the<br>
code that calls criu? Or (!) call criu restore manually on the existing images<br>
with all the options being "correct" by yet again w/o the --restore-sibling?<br>
<span class="HOEnZb"><font color="#888888"><br>
-- Pavel<br>
<br>
</font></span></blockquote></div><br></div>