So, LXD will try to restore containers to whatever state they were in, even if boot.autostart isn't set to true. So that may be what's making this work despite the wrong key being set (user.boot.autostart vs boot.autostart).
In any case, LXD completely ignores all user.* keys as those are for users to put whatever they want in there. Juju definitely needs to be fixed to set boot.autostart instead which is the key that LXD will respect. To recap, current behavior in LXD is: - no boot.autostart set => Attempts to record last container state and restore on reboot (equivalent to power-on-last-state for physical machines) - boot.autostart set to false (never autostart the container, regardless of pre-shutdown state) - boot.autostart set to true (always autostart, regardless of pre-shutdown state). Right now, Juju hits the first of those cases since user.boot.autostart isn't a config key that LXD knows about. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640079 Title: LXDs doesn't start after a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1640079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
