<div dir="ltr">If I run strace on the docker daemon, criu fails to restore with a different error:<div><br></div><div><a href="https://gist.github.com/boucher/bef6e944ae700526a979">https://gist.github.com/boucher/bef6e944ae700526a979</a></div><div>(I included both the restore log and the strace)</div><div><br></div><div>Without strace, I get the same fd already in use error.</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 19, 2015 at 6:00 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 06/19/2015 01:57 AM, Ross Boucher wrote:<br>
> I made some further progress trying to checkpoint/restore nginx in docker. I set things up in the 3.19 kernel and was able to successfully checkpoint the container. Restore failed with this log:<br>
><br>
> <a href="https://gist.github.com/boucher/fa016de5d142988abe3a" rel="noreferrer" target="_blank">https://gist.github.com/boucher/fa016de5d142988abe3a</a><br>
><br>
> Any idea what's going on here?<br>
<br>
</span>(00.032159) 1: File pipe:[44496] will be restored from fd 9 duped from inherit fd 8<br>
(00.032160) 1: Error (util.c:131): fd 5 already in use (called at files.c:872)<br>
<br>
The fd 5 was occupied at the restore time. The easiest way to resolve this is to strace<br>
restoring process (with -f and -s 256 keys) then checking the log where the 5th descriptor<br>
appeared from.<br>
<span class="HOEnZb"><font color="#888888"><br>
-- Pavel<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
><br>
> On Thu, Jun 4, 2015 at 2:18 PM, Pavel Emelyanov <<a href="mailto:xemul@parallels.com">xemul@parallels.com</a> <mailto:<a href="mailto:xemul@parallels.com">xemul@parallels.com</a>>> wrote:<br>
><br>
> On 06/05/2015 12:14 AM, Saied Kazemi wrote:<br>
> > Thanks for the explanation. From your explanation, I assume that back porting Al Viro's patch<br>
> > to 3.18 is not an option. Correct?<br>
><br>
> _Only_ Al's patch -- yes, it wouldn't help. Back-porting both patches -- Al's and<br>
> mine -- will make things work.<br>
><br>
> -- Pavel<br>
><br>
><br>
<br>
</div></div></blockquote></div><br></div>