[lxc-users] lxc 2.0.6 breaks lxc-start

[Christian Brauner]

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?

On Sat, Dec 31, 2016 at 8:46 PM, Serge E. Hallyn <serge at hallyn.com> wrote:
> That looks like
>
> commit 359467743d707d08fda029fa6e957a93bc8dc7ef
> Author: Christian Brauner <christian.brauner at canonical.com>
> Date:   Fri Oct 14 15:27:24 2016 +0200
>
>     tools: better error reporting for lxc-start
>
> which added a check for "!c->is_defined(c)"
>
> Christian?
>
> -serge
>
> Quoting Detlef Vollmann (dv at vollmann.ch):
>> 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 avoid this.
>>
>>   Detlef
>>
>> I'm not on the list, so please CC: me on any replies.
>> _______________________________________________
>> lxc-users mailing list
>> lxc-users at lists.linuxcontainers.org
>> http://lists.linuxcontainers.org/listinfo/lxc-users