I agree, the stage 2 fix for this issue concerns me with regard to regressing current use cases.
As much as I'd like to get rid of the rest of this issue (any user of 10.0.4.0/24 behind a router looses connectivity to that subnet), we must make sure we do not regress anyone who's been relying on "apt-get install lxc" providing something that can immediately be used both by root and for unprivileged users. Serge: We may be able to provide a hook, added to /usr/share/lxc/config/common.conf.d which will bring the bridge up automatically at first lxc container start. Such a hook would unfortunately need to be setuid so that it also works for unprivileged users. We'd also need to make sure that the current lxc hooks are sufficient from a timing point of view to do so (run before lxc checks whether the requested bridge exists). -- 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
