Stuck on Starting container... since upgrade to precise :(
Serge E. Hallyn
serge at hallyn.com
Tue May 1 17:14:11 UTC 2012
Quoting Luis Arias (kaaloo at gmail.com):
> Awesome thanks again! Please see my information below:
>
> On Tue, May 1, 2012 at 6:34 PM, Serge E. Hallyn <serge at hallyn.com> wrote:
>
> > Quoting Luis Arias (kaaloo at gmail.com):
> > > Thank you Serge! I continued some work using an ec2 environment but
> > local
> > > is so much faster!
> > >
> > > This is what's in my /etc/lxc/lxc.conf file which is straight from the
> > > package installation (before the upgrade to precise):
> > >
> > > lxc.network.type=veth
> > > lxc.network.link=lxcbr0
> > > lxc.network.flags=up
> >
> > Can you get a snapshot of /var/lib/lxc/<container>/config while juju
> > is attempting to start one of its containers?
> >
>
> I see a windows style path in there but I don't know enough about lxc to
> tell if it is active and the cause of my issue:
Yes, that is the (pair of) bogus line(s):
> luis at athena:/var/lib/lxc/luis-local-mysql-0$ cat config
> lxc.network.type=veth
> lxc.network.link=virbr0
> lxc.network.flags=up
> lxc.network.hwaddr= 00:16:3e:0c:e4:82
>
> lxc.devttydir = lxc
> lxc.tty = 4
> lxc.pts = 1024
> lxc.arch = amd64
> lxc.cap.drop = sys_module mac_admin
> # uncomment the next line to run the container unconfined:
> #lxc.aa_profile = unconfined
>
> lxc.cgroup.devices.deny = a
> # Allow any mknod (but not using the node)
> lxc.cgroup.devices.allow = c C:\nppdf32Log\debuglog.txt m
> lxc.cgroup.devices.allow = b C:\nppdf32Log\debuglog.txt m
I don't know how this arrived in the config file. Looks like something
tried to process this config file and didn't quote the entries properly.
This bit should read:
lxc.cgroup.devices.allow = c *:* m
lxc.cgroup.devices.allow = b *:* m
Interestingly, other *'s below did not get expanded...
> # /dev/null and zero
> lxc.cgroup.devices.allow = c 1:3 rwm
> lxc.cgroup.devices.allow = c 1:5 rwm
> # consoles
> lxc.cgroup.devices.allow = c 5:1 rwm
> lxc.cgroup.devices.allow = c 5:0 rwm
> #lxc.cgroup.devices.allow = c 4:0 rwm
> #lxc.cgroup.devices.allow = c 4:1 rwm
> # /dev/{,u}random
> lxc.cgroup.devices.allow = c 1:9 rwm
> lxc.cgroup.devices.allow = c 1:8 rwm
> lxc.cgroup.devices.allow = c 136:* rwm
> lxc.cgroup.devices.allow = c 5:2 rwm
> # rtc
> lxc.cgroup.devices.allow = c 254:0 rwm
> #fuse
> lxc.cgroup.devices.allow = c 10:229 rwm
> #tun
> lxc.cgroup.devices.allow = c 10:200 rwm
> #full
> lxc.cgroup.devices.allow = c 1:7 rwm
> #hpet
> lxc.cgroup.devices.allow = c 10:228 rwm
> #kvm
> lxc.cgroup.devices.allow = c 10:232 rwm
> lxc.utsname = luis-local-mysql-0
> lxc.mount = /var/lib/lxc/luis-local-mysql-0/fstab
> lxc.rootfs = /var/lib/lxc/luis-local-mysql-0/rootfs
>
> >
> > If you do:
> >
> > lxc-create -t ubuntu -n p1
> > lxc-start -n p1
> >
> > do you get the same error?
> >
>
> No not at all I get a login prompt!
>
> Ubuntu 12.04 LTS p1 console
>
> p1 login:
>
>
> >
> > > I'll learn more about lxc and see I can dig up a valid value for an
> > > explicit lxc.cgroup.devices.allow setting.
> >
> > You don't need to put those into the /etc/lxc/lxc.conf. The container
> > creation templates put those into /var/lib/lxc/<container>/config.
> > Perhaps juju adds some custom ones as well.
> >
> > -serge
> >
More information about the Juju
mailing list