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" <drbidw...@gmail.com> wrote: > 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-bridge: lxdbr0 > > default-series: trusty > > lxd is configured correctly to use the zfs storage. When I do the juju > bootstrap and deploys, they look like containers but do not show up in > "lxc list". They are also stored in /var/lib/... They look like old > style lxc containers instead of lxd containers. > > What do I need to do differently to get juju to use the lxc launch > containers? > > > -- > Daniel Bidwell <drbidw...@gmail.com> > > > -- > Juju-dev mailing list > juju-...@lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/juju-dev >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
