starting an unprivileged container fails with error 'failed to run autodev hooks for container'

ned

Renowned Member
Jan 26, 2015
113
2
83
I juct sreated mu debian 8 ct as an unprivileged container and got an error 'failed to run autodev hooks for container' .... Is there a way to fix this?
 
Fixed. Open you ct's conf file as /etc/pve/lxc/ID.conf and append
Code:
lxc.autodev: 0
 
Is this a bug? If you ask me this is since you can not create and normally start an unprivileged container....
 
works here without problems, what is the output of
Code:
pveversion -v

the config of the container, and which template do you use?
 
Code:
pveversion -v
proxmox-ve: 4.4-80 (running kernel: 4.4.35-2-pve)
pve-manager: 4.4-12 (running version: 4.4-12/e71b7a74)
pve-kernel-4.4.35-2-pve: 4.4.35-79
pve-kernel-4.4.40-1-pve: 4.4.40-80
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-109
pve-firmware: 1.1-10
libpve-common-perl: 4.0-92
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-73
pve-libspice-server1: 0.12.8-1
vncterm: 1.3-1
pve-docs: 4.4-3
pve-qemu-kvm: 2.7.1-3
pve-container: 1.0-94
pve-firewall: 2.0-33
pve-ha-manager: 1.0-40
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-3
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80


Did you try to create a Debian 8 container in unprivileged mode?
 
This is just a test CT, still did not start.

Code:
arch: amd64
cores: 1
hostname: test.server.com
memory: 1024
net0: name=eth0,bridge=vmbr0,gw=10.10.10.1,hwaddr=4A:76:2B:83:18:EB,ip=10.10.10.198/24,type=veth
onboot: 1
ostype: debian
rootfs: data:vm-198-disk-1,acl=0,quota=1,size=8G
swap: 512
unprivileged: 1
 
yes i installed the template
debian-8.0-standard_8.0-1_amd64.tar.gz and
debian-8.0-standard_8.6-1_amd64.tar.gz
as an unprivileged container and it started without a problem.

what type of storage is "data" ?

i see you did not reboot after a kernel upgrade... maybe this helps?
 
Restart did not help. Storage 'data' is lvm thin type.
 
Last edited:
i now saw that you have quota enabled

this is currently not working with unprivileged container because for quotas we do a mknod (which is not allowed in unprivileged context)

there is a already a bug open (https://bugzilla.proxmox.com/show_bug.cgi?id=1269) which describes a similar problem, maybe you can add your findings there, then you also get a notification when it will be fixed