touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #121484
[Bug 1516971] Re: LXC's preserve_ns fails on < 3.8 kernels
This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.10.3
---------------
lxc (1.1.5-0ubuntu0.15.10.3) wily-proposed; urgency=medium
* Cherry-pick from upstream:
- Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971)
- Fix process title rewrite to not mangle the environment. (LP: #1517107)
lxc (1.1.5-0ubuntu0.15.10.2) wily-proposed; urgency=medium
* Cherry-pick from upstream:
- Fix ubuntu-cloud template to detect compression algorithm instead
of hardcoding xz. Also update list of supported releases and use trusty
as the fallback release. (LP: #1515463)
* Update lxc-tests description to make it clear that this package is
meant to be used by developers and by automated testing.
lxc (1.1.5-0ubuntu0.15.10.1) wily-proposed; urgency=medium
* New upstream bugfix release (MRE) (1.1.5)
(LP: #1497420, LP: #1441068, LP: #1466458, LP: #1510619)
* Drop proxy detection from the autopkgtest exercise script.
-- Stéphane Graber <stgraber@xxxxxxxxxx> Wed, 18 Nov 2015 13:40:28
-0500
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1516971
Title:
LXC's preserve_ns fails on < 3.8 kernels
Status in Canonical System Image:
Fix Released
Status in lxc package in Ubuntu:
Fix Released
Status in lxc source package in Trusty:
Fix Released
Status in lxc source package in Vivid:
Fix Released
Status in lxc source package in Wily:
Fix Released
Status in lxc source package in Xenial:
Fix Released
Bug description:
== SRU ==
Rationale: LXC no longer starts on kernels > 3.2 and < 3.8
Test case: Try starting an LXC container on an affected kernel
Regression potential: Can't really get any worse. Change has been reviewed and tested upstream.
== Original bug report ==
ubuntu-touch/devel-proposed/mako 350
After flashing the device the boot hangs on the vendor logo.
There is no crash file on the device but it seems that the android container fails to start.
There is the following error in syslog
Nov 17 08:33:15 ubuntu-phablet kernel: [ 8.694826] init: lxc-android-config main process (918) terminated with status 255
and in upstart/android.log:
lxc-start 1447749195.286 ERROR lxc_start - start.c:preserve_ns:149 - No such file or directory - failed to open '/proc/1055/ns/mnt'
lxc-start 1447749195.286 ERROR lxc_start - start.c:lxc_spawn:993 - failed to store namespace references
lxc-start 1447749195.408 ERROR lxc_start - start.c:__lxc_start:1192 - failed to spawn 'android'
lxc-start 1447749195.758 ERROR lxc_start_ui - lxc_start.c:main:344 - The container failed to start.
lxc-start 1447749195.758 ERROR lxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516971/+subscriptions