touch-packages team mailing list archive

[Serge Hallyn <1432683@xxxxxxxxxxxxxxxxxx>]

I couldn't reproduce this.  I installed a fresh vivid vm, did apt-get install lxc,
then

ubuntu@lxc-aa:~$ sudo aa-status
apparmor module is loaded.
9 profiles are loaded.
9 profiles are in enforce mode.
   /sbin/dhclient
   /usr/bin/lxc-start
   /usr/lib/NetworkManager/nm-dhcp-client.action
   /usr/lib/NetworkManager/nm-dhcp-helper
   /usr/lib/connman/scripts/dhclient-script
   /usr/sbin/tcpdump
   lxc-container-default
   lxc-container-default-with-mounting
   lxc-container-default-with-nesting

and

ubuntu@lxc-aa:~$ sudo lxc-create -t ubuntu-cloud --name=vivid
[...]
ubuntu@lxc-aa:~$ sudo lxc-start -n vivid
ubuntu@lxc-aa:~$ sudo lxc-ls -f
NAME   STATE    IPV4  IPV6  GROUPS  AUTOSTART
---------------------------------------------
vivid  RUNNING  -     -     -       NO

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

Title:
  apt-get install lxc doesn't load required apparmor profiles

Status in lxc package in Ubuntu:
  New

Bug description:
  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.

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