touch-packages team mailing list archive

[Stéphane Graber <stgraber@xxxxxxxxxxxx>]

Oh, the phone problem is different I think, there the problem is that
your kernel is pretty old and doesn't have the right /proc/self/ns files
available. Looks like that's an actual bug with the new implementation.
I'll report it upstream.

Jean-Baptiste, can you un-duplicate the phone bug and open a lxc task
for it? It's a different issue from what was reported in this bug
report.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1516037

Title:
  lxc-start fails with 1.1.5-0ubuntu1

Status in Canonical System Image:
  Confirmed
Status in apparmor package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Invalid

Bug description:
  After upgrading to lxc 1.1.5-0ubuntu1, lxc-start fails like this:

  lxc-start: start.c: preserve_ns: 149 Permission denied - failed to open '/proc/7170/ns/mnt'
  lxc-start: start.c: lxc_spawn: 993 failed to store namespace references
  lxc-start: start.c: __lxc_start: 1192 failed to spawn 'trusty-lpdev'
  lxc-start: lxc_start.c: main: 344 The container failed to start.
  lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.

  This is with a trusty system container.  precise system containers
  behave similarly.  I don't have others to try.  Downgrading liblxc1,
  lxc, lxc-templates, and python3-lxc to version 1.1.4-0ubuntu3 causes
  lxc-start to work again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516037/+subscriptions