Regarding systemd-specific logic, AFAICT we already have some systemd- specific code for socket activation (see lxd/util/http.go:GetListeners).
I think that conditionally leveraging what systemd offers (in case LXD is managed by systemd), wouldn't be a bad idea, and the strategy proposed by Dimitri sounds robust. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765699 Title: lxd fails to start main process, yet waitready doesn't bail out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1765699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
