<div dir="ltr">:(<div><br></div><div>But, I think we're talking about aufs here and not overlayfs.</div></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Jul 13, 2016 at 1:13 PM 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 Mon, Jul 04, 2016 at 08:55:50PM +0300, Pavel Emelyanov wrote:<br>
> On 06/29/2016 09:07 AM, Andrew Vagin wrote:<br>
> > 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>
> I guess this would be pretty important.<br>
><br>
> Andrey, can you describe what's the issue is from the kernel-to-criu<br>
> communication POV?<br>
<br>
Yesterday I tried to investigate this issue, but<br>
<a href="http://thread.gmane.org/gmane.linux.file-systems.union/826" rel="noreferrer" target="_blank">http://thread.gmane.org/gmane.linux.file-systems.union/826</a><br>
<br>
overlayfs isn't enough stable to work with my karma :-D<br>
<br>
><br>
> -- Pavel<br>
><br>
</blockquote></div>