Quoting Stéphane Graber (stgra...@stgraber.org): > 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).
smoser and I had considered creating a new lxc-base (I'm making that name up) package which is the current lxc without the multi-user.target wants symlink for lxc, and making lxd depend on that package. Regular lxc then would add the multiuser.target wants symlink for lxc. Juju would not regress, regular cloud users would not have lxcbr0 until they used lxd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
