touch-packages team mailing list archive

[Launchpad Bug Tracker <1386840@xxxxxxxxxxxxxxxxxx>]

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 <serge.hallyn@xxxxxxxxxx>   Tue, 11 Nov 2014 14:54:44 -0600

** Changed in: lxc (Ubuntu)
       Status: Triaged => Fix Released

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

Title:
  failure to start a container

Status in “lxc” package in Ubuntu:
  Fix Released
Status in “lxc” source package in Trusty:
  Confirmed
Status in “lxc” source package in Utopic:
  Confirmed

Bug description:
  On utopic using lxc version 1.1.0~alpha2-0ubuntu3, I was unable to
  start a container.

  $ sudo lxc-start -F -n lxc-errors
  lxc-start: lsm/apparmor.c: mount_feature_enabled: 61 Permission denied - Error mounting securityfs
  lxc-start: lsm/apparmor.c: apparmor_process_label_set: 186 If you really want to start this container, set
  lxc-start: lsm/apparmor.c: apparmor_process_label_set: 187 lxc.aa_allow_incomplete = 1
  lxc-start: lsm/apparmor.c: apparmor_process_label_set: 188 in your container configuration file
  lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 4
  lxc-start: start.c: __lxc_start: 1087 failed to spawn 'lxc-errors'
  lxc-start: cgmanager.c: cgm_remove_cgroup: 503 call to cgmanager_remove_sync failed: invalid request
  lxc-start: cgmanager.c: cgm_remove_cgroup: 505 Error removing name=systemd:lxc/lxc-errors-2

  Switching to the version of lxc in http://ppa.launchpad.net/ubuntu-
  lxc/daily/ resolved the failure to start for me.

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