Public bug reported:
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"
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Tags: apparmor systemd-boot
** Tags added: apparmor systemd-boot
--
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/1325468
Title:
[systemd] container startup fails with AppArmor
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1325468/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
