Stuck on Starting container... since upgrade to precise :(

[Serge E. Hallyn]

Quoting Kapil Thangavelu (kapil.thangavelu at canonical.com):
> Excerpts from Serge E. Hallyn's message of 2012-05-01 09:34:33 -0700:
> > 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?
> > 
> > If you do:
> > 
> >     lxc-create -t ubuntu -n p1
> >     lxc-start -n p1
> > 
> > do you get the same error?
> > 
> > > 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
> > 
> 
> fwiw, juju doesn't do anything for config outside of specifying the network 
> flags you posted above.
> 
> cheers,
> 
> Kapil

Heh, no, look at the later details - I think *:* got expanded on a
windows system or in wine :)  I don't believe juju did this.

-serge