Interesting, ok, so with that setup, LXD should absolutely have attempted to bring those containers online.
My best guess is that those network bridges or something related to them didn't exist at the time LXD was started during boot, it then attempted to boot all your containers which failed, explaining the current state. /var/log/lxd/lxd.log may contain some more details as to what happened during boot. -- 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/ubuntu/+source/lxd/+bug/1640079/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
