<div dir="ltr">We may be able to get it merged into experimental without fixing this, but I doubt they will merge this into the main Docker engine without tests, and writing a test is where I'm running into this problem.</div><br><div class="gmail_quote"><div dir="ltr">On Wed, Jun 29, 2016 at 2:07 AM Andrew Vagin <<a href="mailto:avagin@virtuozzo.com">avagin@virtuozzo.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, Jun 28, 2016 at 10:13:13PM +0000, Ross Boucher wrote:<br>
> Andrew, did you have any other thoughts on this?<br>
<br>
> And I ran the exact same commands outside of docker-in-docker just fine,<br>
> so its AUFS docker-in-docker that isn't working I guess.<br>
<br>
How is it critical for us to solve this issue? I am not a big fan of<br>
aufs and overlayfs. Will this issue block a pull-request into Docker?<br>
<br>
><br>
> On Tue, Jun 28, 2016 at 9:49 AM Pavel Emelyanov <<a href="mailto:xemul@virtuozzo.com" target="_blank">xemul@virtuozzo.com</a>> wrote:<br>
><br>
> On 06/23/2016 09:25 AM, Andrew Vagin wrote:<br>
> > On Thu, Jun 23, 2016 at 05:16:24AM +0000, Ross Boucher wrote:<br>
> >> Just updated and posted some comments to that thread.<br>
> ><br>
> > Thanks!<br>
> ><br>
> > Can you try to reproduce this problem with the devicemapper driver?<br>
><br>
> Is it again overlayfs bug?<br>
><br>
> > I think it will work.<br>
> ><br>
> > -- Andrew<br>
> ><br>
> >><br>
> >> On Thu, Jun 23, 2016 at 1:12 AM Andrew Vagin <<a href="mailto:avagin@virtuozzo.com" target="_blank">avagin@virtuozzo.com</a>><br>
> wrote:<br>
> >><br>
> >> On Wed, Jun 22, 2016 at 11:21:48PM +0000, Ross Boucher wrote:<br>
> >> > I've got a checkpoint failure with the automated test I'm trying<br>
> to add<br>
> >> to<br>
> >> > docker. Here's the log:<br>
> >> ><br>
> >> > <a href="https://gist.github.com/boucher/d122da7fc9a93cfb8e6dbe1444791f5f" rel="noreferrer" target="_blank">https://gist.github.com/boucher/d122da7fc9a93cfb8e6dbe1444791f5f</a><br>
> >> ><br>
> >> > From reading the log, it seems like an empty path is trying to be<br>
> >> mounted? I'm<br>
> >> > not sure where that might be coming from. It's probably worth<br>
> noting that<br>
> >> this<br>
> >> > is running docker in docker, but I know we've gotten that to work<br>
> in the<br>
> >> past.<br>
> >><br>
> >> Which storage driver do you use here?<br>
> >> Could you show output for "ls -l /proc/pid/fd /proc/pid/map_files"<br>
> >> for the init process?<br>
> >><br>
> >> > _______________________________________________<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>
> >><br>
> >><br>
> > _______________________________________________<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>
> > .<br>
> ><br>
><br>
><br>
</blockquote></div>