We'd need to see a:
- lxc list
- lxc info
- lxc config show <one of the container names>
When this bug happens, after a reboot, to see what's going on.
LXD is supposed to record the state of all containers on shutdown and restore
them to their last state after reboot, so this suggests that containers were
somehow shutdown prior to your machine being rebooted.
Should there indeed be a bug here, a workaround you can use would be to set
"boot.autostart" to "true" in the default profile with:
lxc profile set default boot.autostart true
Which will effectively force LXD to start all your containers at boot
time, regardless of their state prior to the machine going down.
** Changed in: lxd (Ubuntu)
Status: New => Incomplete
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
