*** This bug is a duplicate of bug 1296459 ***
https://bugs.launchpad.net/bugs/1296459
I don't know if this bug is really a duplicate but i encountered it
today.
I had to poweroff then restart our proxmox server, and 2 lxc containers refused
to start with this error :
lxc-start 20170119130520.594 ERROR lxc_apparmor -
lsm/apparmor.c:apparmor_process_label_set:234 - No such file or directory -
failed to change apparmor profile to lxc-container-default-cgns
lxc-start 20170119130520.595 ERROR lxc_sync - sync.c:__sync_wait:57 - An
error occurred in another process (expected sequence number 5)
lxc-start 20170119130520.595 ERROR lxc_start - start.c:__lxc_start:1357 -
Failed to spawn container "105".
lxc-start 20170119130521.359 ERROR lxc_conf - conf.c:run_buffer:347 - Script
exited with status 32
lxc-start 20170119130521.359 ERROR lxc_start - start.c:lxc_fini:546 - Failed
to run lxc.hook.post-stop for container "105".
Adding "lxc.aa_profile = unconfined" fixed the issue.
# pveversion --verbose
proxmox-ve: 4.4-78 (running kernel: 4.4.35-2-pve)
pve-manager: 4.4-5 (running version: 4.4-5/c43015a5)
pve-kernel-4.4.13-1-pve: 4.4.13-56
pve-kernel-4.4.35-1-pve: 4.4.35-77
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.4.8-1-pve: 4.4.8-52
pve-kernel-4.4.13-2-pve: 4.4.13-58
pve-kernel-4.4.35-2-pve: 4.4.35-78
pve-kernel-4.4.21-1-pve: 4.4.21-71
pve-kernel-4.4.15-1-pve: 4.4.15-60
pve-kernel-4.4.24-1-pve: 4.4.24-72
pve-kernel-4.4.19-1-pve: 4.4.19-66
pve-kernel-4.4.10-1-pve: 4.4.10-54
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-102
pve-firmware: 1.1-10
libpve-common-perl: 4.0-85
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-71
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-1
pve-qemu-kvm: 2.7.1-1
pve-container: 1.0-90
pve-firewall: 2.0-33
pve-ha-manager: 1.0-38
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.6-5
lxcfs: 2.0.5-pve2
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296681
Title:
failed to change apparmor profile to lxc-container-default
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1296681/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
