[Bug 987371] Re: unconfined containers are not starting

2012-08-07 Thread Serge Hallyn
** Changed in: lxc (Ubuntu Precise) Status: New = Invalid ** Changed in: apparmor (Ubuntu Precise) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu.

[Bug 987371] Re: unconfined containers are not starting

2012-06-25 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/precise-proposed/linux-armadaxp -- 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/987371 Title: unconfined containers are not starting To manage notifications

[Bug 987371] Re: unconfined containers are not starting

2012-06-13 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 3.2.0-25.40 --- linux (3.2.0-25.40) precise-proposed; urgency=low [Luis Henriques] * Release Tracking Bug - LP: #1003534 [ Andy Whitcroft ] * [Config] control.stub is an intermediate product not a dependancy - LP: #992414

[Bug 987371] Re: unconfined containers are not starting

2012-06-01 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/precise-proposed/linux-ti-omap4 -- 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/987371 Title: unconfined containers are not starting To manage notifications

[Bug 987371] Re: unconfined containers are not starting

2012-05-28 Thread Luis Henriques
This bug is awaiting verification that the kernel for precise in -proposed solves the problem (3.2.0-25.40). Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-precise' to 'verification-done-precise'. If verification is not

[Bug 987371] Re: unconfined containers are not starting

2012-05-28 Thread Stéphane Graber
Confirmed on a precise VM, lxc.aa_profile = unconfined now works as expected. Testing a few other containers I couldn't spot any obvious regression. ** Tags removed: verification-needed-precise ** Tags added: verification-done-precise -- You received this bug notification because you are a

[Bug 987371] Re: unconfined containers are not starting

2012-05-25 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 3.4.0-3.8 --- linux (3.4.0-3.8) quantal; urgency=low [ Andy Whitcroft ] * [Config] include include/generated/compile.h - LP: #942569 * [Config] fix up postinst to ensure we know which error is which - LP: #1002388 [ Herton

[Bug 987371] Re: unconfined containers are not starting

2012-05-22 Thread Tim Gardner
** Also affects: apparmor (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Quantal)

[Bug 987371] Re: unconfined containers are not starting

2012-05-02 Thread Christopher Armstrong
It looks like this bug prevents switching to ANY profile, not just unconfined. -- 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/987371 Title: unconfined containers are not starting To

[Bug 987371] Re: unconfined containers are not starting

2012-05-02 Thread Serge Hallyn
@Christopher, To support switching to any other profile than unconfined or lxc-*, you need to add a transition rule to /etc/apparmor.d/local/usr.bin.lxc- start (see /etc/apparmor.d/usr.bin.lxc-start for the default profile). If you still have trouble, please open a new bug, showing the relevant

[Bug 987371] Re: unconfined containers are not starting

2012-05-02 Thread Christopher Armstrong
My mistake, it is working to switch to different containers. I think I just hadn't actually reloaded my apparmor profiles when I tried using the one I had just created. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu.

[Bug 987371] Re: unconfined containers are not starting

2012-04-23 Thread Serge Hallyn
Sorry, the relevant error message is: lxc-start: No such file or directory - failed to change apparmor profile to unconfined -- 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/987371 Title:

[Bug 987371] Re: unconfined containers are not starting

2012-04-23 Thread John Johansen
I have a test kernel at http://people.canonical.com/~jj/linux- image-3.2.0-23-generic_3.2.0-23.36~aa_amd64.deb and believe this to be the same as Bug #978038 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu.

[Bug 987371] Re: unconfined containers are not starting

2012-04-23 Thread Serge Hallyn
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/987371 Title: unconfined containers are not starting To

[Bug 987371] Re: unconfined containers are not starting

2012-04-23 Thread Serge Hallyn
That kernel fixes it, thanks. ** Changed in: linux (Ubuntu) Status: Incomplete = Fix Committed ** Changed in: apparmor (Ubuntu) Status: New = Invalid ** Changed in: lxc (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of