On 01/09/16 10:17, John Meinel wrote:
>
> 1.25 does not support LXD managed containers as it uses the old
> lxc-foo CLI to manage containers (lxc-start is not the same as "lxc
> start").
> juju-2.0 will use LXD managed containers but there are no plans to
> backport that support to 1.25
>
To be cl
1.25 does not support LXD managed containers as it uses the old lxc-foo CLI
to manage containers (lxc-start is not the same as "lxc start").
juju-2.0 will use LXD managed containers but there are no plans to backport
that support to 1.25
John
=:->
On Sep 1, 2016 4:12 PM, "Daniel Bidwell" wrote:
Hi Daniel
The transition from "1.0 everything" to "2.0 everything" is significant.
1.x Juju, 1.x MAAS and 1.x LXC all line up pretty well, as do 2.x MAAS,
2.x LXC/D, and 2.x Juju.
Crossing wires between those is not very easy at the moment - we do
intend to provide upgrade mechanisms but are focu
I have juju-1.25.6 on xenial and am trying to configure it to use the
local lxc containers. I have lxd configured to use a zfs volume for
containers. My .juju/environment.yaml looks like:
local:
type: local
lxc-clone: true
root-dir: /envision/lxc
network-bri
