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 focused on the GA 2.x releases initially. My recommendation would be to focus on the 2.x series of all of these unless you require to be in production before 16.10. Apologies that might be a tough choice, but I think you'll find that the 2.x series benefits outweigh the timeline impact in most cases. Mark On 01/09/16 08:12, Daniel Bidwell 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? > > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
