<div dir="ltr">Andrew, thank you for reporting and providing an easy way to reproduce the problem.<div><br></div><div>Miklos, thanks for the quick reply. If you'd like to see the issue with checkpointing and restoring Docker containers using OverlayFS, you can use the docker binary here <a href="https://github.com/SaiedKazemi/docker/releases">https://github.com/SaiedKazemi/docker/releases</a>.</div><div><br></div><div>--Saied</div><div><br><div><br></div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 15, 2015 at 8:07 AM, Miklos Szeredi <span dir="ltr"><<a href="mailto:miklos@szeredi.hu" target="_blank">miklos@szeredi.hu</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 Wed, Apr 15, 2015 at 10:50 AM, Andrew Vagin <<a href="mailto:avagin@odin.com">avagin@odin.com</a>> wrote:<br>
> Hello Miklos and Everyone else,<br>
><br>
> We have a report that a container with overlayfs can't be checkpointed.<br>
><br>
> To dump file descriptors we get information from /proc/pid/fd/ and /proc/pid/fdinfo.<br>
><br>
> But in case of overlayfs we see unexpected values there.<br>
><br>
> /proc/PID/fdinfo/FD contains mnt_id which isn't presented in /proc/pid/mountinfo.<br>
> /proc/PID/fd/FD does not contain an absolute path to the opened file.<br>
><br>
> Can someone help to fix these issues?<br>
<br>
</span>See this:<br>
<br>
<a href="https://lkml.org/lkml/2015/3/20/372" target="_blank">https://lkml.org/lkml/2015/3/20/372</a><br>
<br>
Al didn't like that patch. But it definitely will be fixed, one way<br>
or the other, in the near future.<br>
<br>
Thanks,<br>
Miklos<br>
</blockquote></div><br></div>