<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 5, 2015 at 8:18 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 08/05/2015 05:24 AM, Z F wrote:<br>
> Hi,<br>
><br>
</span><span class="">> About file sizes:<br>
><br>
> //In containers<br>
> bash-4.2# ls -lt /usr/bin/bash<br>
> -rwxr-xr-x. 1 root root 960392 Sep 25 2014 /usr/bin/bash<br>
> bash-4.2#<br>
> //In host<br>
> [root@compute2 dockerbins]# ls -lt /usr/bin/bash<br>
> -rwxr-xr-x. 1 root root 960384 Sep 26 2014 /usr/bin/bash<br>
> [root@compute2 dockerbins]#<br>
><br>
><br>
><br>
> About FS: I am using VFS.<br>
><br>
><br>
><br>
> As explained in the <a href="http://criu.org/Docker" rel="noreferrer" target="_blank">http://criu.org/Docker</a>, --root is necessary for AUFS only. Then I suppose --root is not necessary for VFS, then the container's root filesystem would be at the default /var/lib/docker/containers/<container-id>/. Is that correct?<br></span></blockquote><div><br></div><div><div>I know it can be confusing... I didn't mean the --root command line option. I was saying the root of the container has be bind mounted onto itself. This is implicitly done for AUFS when it's set up but for VFS, has to be done explicitly. You can look at prep_restore() in contrib/docker_cr.sh.<br></div></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
><br>
> About mount, 3 cases tested:<br>
> 1. No --root, no mount --rbind: bad file size error.<br>
> 2. No --root, mount --rbind: bad file size error.<br>
> 3. docker_cr.sh:<br>
> (00.011447) 1: Error (mount.c:1861): Can't mount at ./proc: No such file or directory<br>
> (00.034211) Error (cr-restore.c:1219): 63981 exited, status=1<br>
> (00.034228) Error (cr-restore.c:1912): Restoring FAILED.<br>
<br>
</span>(00.011392) 1: ----------------------------> Try to validate ./etc/resolv.conf<br>
(00.011395) 1: ----------------------------> Try to validate ./etc/hostname<br>
(00.011397) 1: ----------------------------> Try to validate ./etc/hosts<br>
(00.011404) 1: ----------------------------> Try to validate ./proc/sys<br>
(00.011407) 1: ----------------------------> Try to validate ./proc/sysrq-trigger<br>
(00.011409) 1: ----------------------------> Try to validate ./proc/irq<br>
(00.011411) 1: ----------------------------> Try to validate ./proc/bus<br>
(00.011413) 1: ----------------------------> Try to validate ./proc/kcore<br>
<br>
There's no such print-s in criu code :)<br>
<br>
(00.011416) 1: 146:./ private 1 shared 0 slave 0<br>
(00.011420) 1: Start with 146:./<br>
(00.011423) 1: Mounting unsupported @./ (0)<br>
(00.011428) 1: Mounting proc @./proc (0)<br>
<span class="">(00.011447) 1: Error (mount.c:1861): Can't mount at ./proc: No such file or directory<br>
<br>
</span>Hm... No proc directory in the root you've specified.<br>
<span class="HOEnZb"><font color="#888888"><br>
-- Pavel<br>
</font></span></blockquote></div><br></div></div>