touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Stéphane pointed out on IRC the other day that "in (rw, slave)" is too
lax, but that "=(rw, slave)" would be okay. I'll add that now, as this
is both really hard to discover, as well as leaves quite a lot of
garbage (mounts) behind on failures.

** Changed in: lxc (Ubuntu)
       Status: Triaged => In Progress

** Changed in: lxc (Ubuntu)
     Assignee: (unassigned) => Martin Pitt (pitti)

-- 
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/1325468

Title:
  [systemd] container startup fails with AppArmor

Status in “lxc” package in Ubuntu:
  In Progress

Bug description:
  When booting with systemd, and manually setting up lxcbr0 (bug
  1312532), container startup fails with:

  $ sudo lxc-start -n adt-utopic
  lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1; continuing
  lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1; continuing
  lxc-start: Permission denied - Failed to make / rslave
  lxc-start: Continuing...
  lxc-start: Input/output error - error 5 creating /usr/lib/x86_64-linux-gnu/lxc/dev/lxc/console
  lxc-start: failed to setup the console for 'adt-utopic'
  lxc-start: failed to setup the container
  lxc-start: invalid sequence number 1. expected 2
  lxc-start: failed to spawn 'adt-utopic'

  The relevant kernel error:
  [ 1086.599639] audit: type=1400 audit(1401687485.695:171): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="/usr/bin/lxc-start" name="/" pid=10125 comm="lxc-start" flags="rw, rslave"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1325468/+subscriptions