[Bug 1386840] Re: failure to start a container

2015-02-03 Thread Felipe Reyes
Patch to backport the fix into utopic. ** Description changed: + [Impact] + + Without this patch containers that don't have a complete apparmor + configuration fail to start. Making lxc unusable to run Debian Sid and Jessie + (at least). + + This bug is not present in Trusty, which ships 1.0.7

[Bug 1386840] Re: failure to start a container

2015-02-02 Thread Felipe Reyes
** Changed in: lxc (Ubuntu Trusty) Assignee: (unassigned) => Felipe Reyes (freyes) ** Changed in: lxc (Ubuntu Utopic) Assignee: (unassigned) => Felipe Reyes (freyes) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bu

[Bug 1386840] Re: failure to start a container

2014-11-11 Thread Launchpad Bug Tracker
This bug was fixed in the package lxc - 1.1.0~alpha2-0ubuntu7 --- lxc (1.1.0~alpha2-0ubuntu7) vivid; urgency=medium * Cherrypick 0010-apparmor-check-for-mount-feature-at-a-better-time.patch from upstream to fix startup failure with certain setups (LP: #1386840) -- Serge Hallyn

[Bug 1386840] Re: failure to start a container

2014-11-11 Thread Serge Hallyn
I am pushing lxc_1.1.0~alpha2-0ubuntu7 which should fix this bug. I'm hoping someone will SRU the patch to T and U. Note that any container which actually specifies the securityfs mount in its config (as the default unprivileged ubuntu configs do) should not have this problem. -- You received t

[Bug 1386840] Re: failure to start a container

2014-11-10 Thread maxadamo
This the workaround: apt-get install apparmor-utils aa-complain /usr/bin/lxc-start here, I think, there should be the solution: https://lists.linuxcontainers.org/pipermail/lxc-devel/2014-October/010662.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1386840] Re: failure to start a container

2014-11-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu Trusty) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386840 Title:

[Bug 1386840] Re: failure to start a container

2014-11-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu Utopic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386840 Title:

[Bug 1386840] Re: failure to start a container

2014-10-28 Thread Serge Hallyn
** Changed in: lxc (Ubuntu) Importance: Undecided => High ** Changed in: lxc (Ubuntu) Status: New => Triaged ** Also affects: lxc (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Utopic) Importance: Undecided Status: New -- You receiv