If you have a container or images, you can't run LXD init, because it would potentially change the storage backend, etc. If you already had LXD up and running, what were you looking to do with LXD init ? It is possible that you could delete all of your instances and images and then run it. Or you could directly set the configuration you need "lxc config set ???". You can set core.trust_password, core.https_address. I don't think you can set the storage backend, because then you'd have to migrate all of your data over, which is the same thing as deleting it and running 'lxd init' and then starting fresh.
John =:-> On Thu, May 12, 2016 at 12:35 AM, Daniel Bidwell <[email protected]> wrote: > I just upgraded a machine to 16.04 and tried to do an "lxd init" and > received an err of "LXD init cannot be used at this time". What causes > this? What do I have to clear out to make it work correctly? > -- > Daniel Bidwell <[email protected]> > > > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
