lxd provider in master

[Tim Penhey]

On 24/11/15 04:53, Eric Snow wrote:
> On Sun, Nov 22, 2015 at 8:50 PM, Tim Penhey <tim.penhey at canonical.com> wrote:
>> Hi all,
>>
>> I noticed that the lxd provider was now in master and attempted to use
>> it to help debug an HA problem.
>>
>> In environments.yaml file I added a very simple clause:
>>
>>    lxd:
>>       type: lxd
> 
> This is what I've been using.  It works fine.
> 
> This helps identify the problem.  The environment you tried to
> bootstrap has "container: lxd" and there is no "lxd" container type.
> Perhaps it's an old environment, set up back when the LXD provider was
> first prototyped (with its own container type)?  It does not appear to
> be the simple "lxd" environment you showed above.
> 
> Also, FYI, "namespace" is still around but is not necessary.  It is
> useful when you want to have multiple LXD providers running on your
> local LXD.

found that further down the file I found this:

    lxd:
       type: local
       container: lxd

That was causing problems :-)

Got it bootstrapped now.

Tim