I tried to test pivot_root from command line after an unsuccessful
container start:
# cd /mnt/lxc
# ls
bin boot dev etc home lib lib64 media mnt opt proc root run sbin
selinux srv sys tmp usr var
# ls mnt
# pivot_root . /mnt/lxc/mnt
pivot_root: Invalid argument
Ther
> "DB" == Daniel Baumann writes:
DB> i've fixed that in git some time ago but didn't upload it yet.
DB> please redo with lxc built from the debian branch of
DB> git://vcs.progress-linux.org/users/daniel/packages/lxc.git
The first container creation problem is fixed but the second
i've fixed that in git some time ago but didn't upload it yet.
please redo with lxc built from the debian branch of
git://vcs.progress-linux.org/users/daniel/packages/lxc.git
--
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email: daniel.baum...@progress-technologies.ne
With lxc 0.7.5-24 container creation works and the container startup
problem is the same:
# lxc-start -n foo
lxc-start: Invalid argument - pivot_root syscall failed
lxc-start: failed to setup pivot root
lxc-start: failed to set rootfs for 'foo'
lxc-start: failed to setup the container
> "DB" == Daniel Baumann writes:
DB> create a 'default' wheezy container with 'lxc-create -t debian
DB> -n foo'.
This doesn't work:
# lxc-create -t debian -n foo
Note: Usually the template option is called with a configuration
file option too, mostly to configure the netwo
On 03/30/2012 12:59 AM, Milan Zamazal wrote:
> I've no idea whether the pivot_root call should succeed or not under
> these circumstances.
create a 'default' wheezy container with 'lxc-create -t debian -n foo'.
can you start it with 'lxc-start -n foo'?
--
Address:Daniel Baumann, Donnerbu
So the failure happens in the call
pivot_root(".", path)
in conf.c:setup_rootfs_pivot_root, with the error message "Invalid
argument". `path' value is "/mnt/lxc/mnt", current directory is
"/mnt/lxc". This seems to be correct, or at least intended. The
directories in /mnt/lxc are mounted as f
severity 663274 normal
tag 663274 moreinfo
tag 663274 unreproducible
thanks
it's not reproducible on any clean system of mine, neither on amd64 nor
i386.
--
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email: daniel.baum...@progress-technologies.net
Internet: htt
I've got the same problem, with both lxc 0.7.5 and lxc 0.8.0~rc1-3.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: lxc
Version: 0.8.0~rc1-2
Severity: important
This is probably related to #663062, possibly a dup.
I haven't rebooted my system in a few months, so I haven't noticed this until
now:
Prior to the reboot, I was using kernel 3.2.0-1-amd64, post-reboot is
3.2.0-2-amd64 (I've done several boo
10 matches
Mail list logo
