Quoting Stéphane Graber (<email address hidden>):
> 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.
Quoting Stéphane Graber (<email address hidden>): lxc/config/ common. conf.d which will bring the bridge up
> 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/
> 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.