Public bug reported:
I'm trying to use LXC on my openstack instance which runs vivid daily:
$ sudo apt-get install lxc -y
$ sudo lxc-create -t ubuntu-cloud --name=vivid -- --flush-cache
--stream=daily --release=vivid
$ sudo lxc-start --name vivid --logfile=lxc.log
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in
foreground mode.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by
setting the --logfile and --logpriority options.
In the log file (lxc.log) I observe the following error:
lxc-start 1426516387.814 ERROR lxc_apparmor -
lsm/apparmor.c:apparmor_process_label_set:183 - No such file or directory -
failed to change apparmor profile to lxc-container-default
This profile *exists* under /etc/apparmor.d/lxc/lxc-default but was not
loaded appropriately.
This issue disappears if I:
(a) reload apparmor profile manually: sudo /etc/init.d/apparmor reload
or
(b) reboot the instance
I'd expect that 'apt-get install lxc' has to load all appropriate
apparmor profiles to allow starting containers w/o profile reloading /
rebooting.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
I'm trying to use LXC on my openstack instance which runs vivid daily:
$ sudo apt-get install lxc -y
$ sudo lxc-create -t ubuntu-cloud --name=vivid -- --flush-cache
--stream=daily --release=vivid
$ sudo lxc-start --name vivid --logfile=lxc.log
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in
foreground mode.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by
setting the --logfile and --logpriority options.
In the log file (lxc.log) I observe the following error:
lxc-start 1426516387.814 ERROR lxc_apparmor -
lsm/apparmor.c:apparmor_process_label_set:183 - No such file or directory -
failed to change apparmor profile to lxc-container-default
This profile *exists* under /etc/apparmor.d/lxc/lxc-default but was not
loaded appropriately.
This issue disappears if I:
(a) reload apparmor profile manually: sudo /etc/init.d/apparmor reload
or
(b) reboot the instance
- I'd expert that 'apt-get install lxc' has to load all appropriate
+ I'd expect that 'apt-get install lxc' has to load all appropriate
apparmor profiles to allow starting containers w/o profile reloading /
rebooting.
--
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/1432683
Title:
apt-get install lxc doesn't load required apparmor profiles
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1432683/+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
