[CRIU] CRIU Docker Restore with Error: Bad File Size

Saied Kazemi saied at google.com
Wed Aug 5 10:14:07 PDT 2015


On Wed, Aug 5, 2015 at 8:18 AM, Pavel Emelyanov <xemul at parallels.com> wrote:

> On 08/05/2015 05:24 AM, Z F wrote:
> > Hi,
> >
> > About file sizes:
> >
> > //In containers
> > bash-4.2# ls -lt /usr/bin/bash
> > -rwxr-xr-x. 1 root root 960392 Sep 25  2014 /usr/bin/bash
> > bash-4.2#
> > //In host
> > [root at compute2 dockerbins]# ls -lt /usr/bin/bash
> > -rwxr-xr-x. 1 root root 960384 Sep 26  2014 /usr/bin/bash
> > [root at compute2 dockerbins]#
> >
> >
> >
> > About FS: I am using VFS.
> >
> >
> >
> > As explained in the http://criu.org/Docker, --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?
>

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.



> >
> > About mount, 3 cases tested:
> > 1. No --root, no mount --rbind:  bad file size error.
> > 2. No --root, mount --rbind: bad file size error.
> > 3. docker_cr.sh:
> > (00.011447)      1: Error (mount.c:1861): Can't mount at ./proc: No such
> file or directory
> > (00.034211) Error (cr-restore.c:1219): 63981 exited, status=1
> > (00.034228) Error (cr-restore.c:1912): Restoring FAILED.
>
> (00.011392)      1: ----------------------------> Try to validate
> ./etc/resolv.conf
> (00.011395)      1: ----------------------------> Try to validate
> ./etc/hostname
> (00.011397)      1: ----------------------------> Try to validate
> ./etc/hosts
> (00.011404)      1: ----------------------------> Try to validate
> ./proc/sys
> (00.011407)      1: ----------------------------> Try to validate
> ./proc/sysrq-trigger
> (00.011409)      1: ----------------------------> Try to validate
> ./proc/irq
> (00.011411)      1: ----------------------------> Try to validate
> ./proc/bus
> (00.011413)      1: ----------------------------> Try to validate
> ./proc/kcore
>
> There's no such print-s in criu code :)
>
> (00.011416)      1: 146:./ private 1 shared 0 slave 0
> (00.011420)      1: Start with 146:./
> (00.011423)      1:     Mounting unsupported @./ (0)
> (00.011428)      1:     Mounting proc @./proc (0)
> (00.011447)      1: Error (mount.c:1861): Can't mount at ./proc: No such
> file or directory
>
> Hm... No proc directory in the root you've specified.
>
> -- Pavel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20150805/9b2836bb/attachment-0001.html>


More information about the CRIU mailing list