A pre-start lxc hook with sufficient privileges to start lxc-net would cover all use cases as far as I can tell and would only require the addition of two files to the lxc package.
Such a hook would also cover LXD as LXD does exec all LXC hooks, so we wouldn't even have to mess with those init scripts at all. Just ship such a hook and have the cloud-images ship with the lxc-net job disabled. At container startup time, the hook fires and if the job isn't running, it gets started. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
