** Changed in: lxc (Ubuntu Trusty)
Status: Incomplete => Fix Released
--
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/1386840
Title:
[SRU] failure to start a container
To manage
This bug was fixed in the package lxc - 1.1.0~alpha2-0ubuntu3.2
---
lxc (1.1.0~alpha2-0ubuntu3.2) utopic; urgency=medium
* Cherrypick 0007-apparmor-check-for-mount-feature-at-a-better-time.patch
from upstream to fix startup failure with certain setups (LP: #1386840)
-- Felipe
Using 1.1.0~alpha2-0ubuntu3.2 fixes the issue. Thanks!
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1386840
Hello Brian, or anyone else affected,
Accepted lxc into utopic-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/lxc/1.1.0~alpha2-0ubuntu3.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Sponsored for Utopic.
--
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/1386840
Title:
[SRU] failure to start a container
To manage notifications about this bug go to:
Here I'm attaching a patch built on top of the latest version of the
package (1.1.0~alpha2-0ubuntu3.1)
** Patch removed: utopic_lp1386840.debdiff
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1386840/+attachment/4311145/+files/utopic_lp1386840.debdiff
** Patch added:
** Tags added: cts
--
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/1386840
Title:
[SRU] failure to start a container
To manage notifications about this bug go to:
