This is what I get on a trusty vagrant box with latest kernel, lxc and apparmor from trusty-updates:
root@vagrant-ubuntu-trusty-64:~# lxc-execute --name guest -- echo foobar lxc-execute: utils.c: safe_mount: 1391 No such file or directory - Failed to mount proc onto /proc lxc-execute: conf.c: tmp_proc_mount: 4132 No such file or directory - failed to mount /proc in the container. lxc-execute: lsm/apparmor.c: apparmor_process_label_get: 80 No such file or directory - opening /proc/1/attr/current lxc-execute: lsm/apparmor.c: apparmor_process_label_set: 191 No such file or directory - failed to change apparmor profile to lxc-container-default lxc-execute: sync.c: __sync_wait: 57 An error occurred in another process (expected sequence number 5) lxc-execute: start.c: __lxc_start: 1149 failed to spawn 'guest' This is what I get on a trusty vagrant box with lxc and apparmor from trusty-security: root@vagrant-ubuntu-trusty-64:~# lxc-execute --name test -- echo foobar lxc: cgmanager.c: lxc_cgmanager_escape: 331 call to cgmanager_move_pid_abs_sync(hugetlb) failed: Escape request from different namespace requires a proxy init.lxc: initutils.c: mount_fs: 36 failed to mount /proc : Device or resource busy foobar Note that no foobar is shown in the first scenario, so something seems broken on the recent updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659590 Title: containers won't start after lxc and apparmor upgrades in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1659590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
