[Bug 1312532] Re: [systemd] Container startup fails on missing lxcbr0

2014-04-29 Thread Martin Pitt
For the record, this is the broken-out shell script which should factorize init.d/unit/upstart job. I tried to run sudo mount --make-rprivate / to work around that AA issue. Now sudo ./lxc-net start fails with $ sudo lxc-start -n debci lxc-start: Device or resource busy - failed to set

[Bug 1312532] Re: [systemd] Container startup fails on missing lxcbr0

2014-04-28 Thread Serge Hallyn
I think the apparmor issue should be filed as a separate bug. The issue there is that systemd has mounted / as MS_SHARED, so lxc is having to remount / as rslave. The apparmor policy will need to be updated to allow that. Ideally we can wait to allow that until the apparmor parser properly

[Bug 1312532] Re: [systemd] Container startup fails on missing lxcbr0

2014-04-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu) Status: New = Confirmed -- 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/1312532

[Bug 1312532] Re: [systemd] Container startup fails on missing lxcbr0

2014-04-25 Thread Martin Pitt
For the record: I turned /etc/init/lxc-net.conf into a shell script that you call with start or stop. With that we can keep the logic in one place, and the upstart/systemd/init.d script would just call this. That sets up the lxcbr interface etc. I also ran the apparmor bits from