"Cannot mknod: Operation not permitted" when installing Turnkey Redis CT

[jrjsmrtn]

Hello,

I'm trying to deploy a Redis container using the Turnkey Linux Redis 15.0-1 template but it fails miserably with the following errors:

tar: ./var/spool/postfix/dev/urandom: Cannot mknod: Operation not permitted​

tar: ./var/spool/postfix/dev/random: Cannot mknod: Operation not permitted​

Does anybody got those errors? Other TKL templates worked fine.

I suppose it's more a Turnkey Linux issue than a Proxmox one, but I wanted to ask here first.

The complete log is:

Logical volume "vm-120-disk-0" created.
mke2fs 1.44.5 (15-Dec-2018)
Discarding device blocks:    4096/2097152               done                           
Creating filesystem with 2097152 4k blocks and 524288 inodes
Filesystem UUID: 1c66794a-32e3-4123-be45-f09775cb4159
Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

Allocating group tables:  0/64     done                           
Writing inode tables:  0/64     done                           
Creating journal (16384 blocks): done
Multiple mount protection is enabled with update interval 5 seconds.
Writing superblocks and filesystem accounting information:  0/64     done

extracting archive '/mnt/pve/yoda/template/cache/debian-9-turnkey-redis_15.0-1_amd64.tar.gz'
tar: ./var/spool/postfix/dev/urandom: Cannot mknod: Operation not permitted
tar: ./var/spool/postfix/dev/random: Cannot mknod: Operation not permitted
Total bytes read: 848271360 (809MiB, 108MiB/s)
tar: Exiting with failure status due to previous errors
  Logical volume "vm-120-disk-0" successfully removed
TASK ERROR: unable to create CT 120 - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- tar xpf - -z --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.*' '--xattrs-include=security.capability' '--warning=no-file-ignored' '--warning=no-xattr-write' -C /var/lib/lxc/120/rootfs --skip-old-files --anchored --exclude './dev/*'' failed: exit code 2

Thanks in advance...

 

[dietmar]

You need to run that as "privileged" container (unless turnkey remove those device nodes).

 

[jrjsmrtn]

(facepalm)

Thanks