The error appears on bootstrap like this: $ juju bootstrap mycontroller lxd Creating Juju controller "mycontroller" on lxd/localhost Bootstrapping model "mycontroller" Starting new instance for initial controller Launching instance ERROR failed to bootstrap model: cannot start bootstrap instance: can't get info for image 'ubuntu-trusty': json: cannot unmarshal string into Go value of type int64
https://bugs.launchpad.net/juju-core/+bug/1547268 Also affects Juju 2.0 alpha2 On 21/02/16 16:46, Mark Shuttleworth wrote: > On 21/02/16 00:18, Ian Booth wrote: >> It seems the confusion comes from not seeing lxd in the output of juju >> list-clouds. list-clouds ostensibly shows available public clouds (aws, azure >> etc) and any private clouds (maas, openstack etc) added by the user. The lxd >> cloud is just built-in to Juju. But from a usability perspective, it's seems >> we >> should include lxd in the output of list-clouds. > > Yes please :) > >> NOTE: the latest lxd 2.0.0 beta3 release recently added to the archives has >> an >> api change that is not compatible with Juju. You will need to ensure that >> you're >> still using the lxd 2.0.0 beta2 release to test with Juju. > > Is that the source of the error: > > ERROR invalid config: Can not change ZFS config. Images or containers > are still using the ZFS pool: > > ? > > Mark > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
