Re: [lxc-users] lxc 2.0.6 breaks lxc-start

2017-01-21 Thread Detlef Vollmann
On 01/11/17 16:24, Christian Brauner wrote: > I sent a branch against lxc (https://github.com/lxc/lxc/pull/1381) which > removes > the c->is_defined(c) check. Thanks a lot! I'll don't test it right now (sorry, just too lazy to compile it myself), but I'm sure I'll get it pretty soon via the PPA,

Re: [lxc-users] lxc 2.0.6 breaks lxc-start

2017-01-21 Thread Detlef Vollmann
Hi Christian, thank you for replying! On 01/09/17 17:35, Christian Brauner wrote: > Thanks for the info. I'm a little confused. Sorry about that. But maybe it's because we talk about different things. > On Thu, Jan 05, 2017 at 01:31:28PM +0100, Detlef Vollmann wrote: >> On 01

Re: [lxc-users] lxc 2.0.6 breaks lxc-start

2017-01-08 Thread Detlef Vollmann
On 01/01/17 14:14, Christian Brauner wrote: > Hm, works for me. I can just start containers fine where the > configuration file is located somewhere else. Can you please > append/copy the containers configuration file here and note any > special tweaks to your setup as well? Here's my test case: $

[lxc-users] lxc 2.0.6 breaks lxc-start

2016-12-26 Thread Detlef Vollmann
Hello, I typically start my containers with something like: sudo lxc-start -F -n xenial-dev -f /images/lxc/xenial-dev.conf With 2.0.6, I get the error 'Error: container xenial-dev is not defined' Going back to 2.0.5 solves the problem. Using lxc-create also solves the problem, but I want to