Probleme mit TurnKey Templates

apachler

Member
Jul 8, 2016
25
1
23
41
Hallo liebe Forengemeinde,

ich habe heute zum ersten mal versucht einen LXC Container mit einem TurnKey Template zu erstellen, leider ohne Erfolg. Hab das natürlich auch mit mehreren Versuch ;)

Proxmox Version ist: pve-manager/4.4-15/7599e35a

Code:
/dev/rbd3
mke2fs 1.42.12 (29-Aug-2014)
Discarding device blocks: 4096/2097152 done
Creating filesystem with 2097152 4k blocks and 524288 inodes
Filesystem UUID: baf18ad1-b1aa-4e01-9703-9168e477c8ea
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 (32768 blocks): done
Multiple mount protection is enabled with update interval 5 seconds.
Writing superblocks and filesystem accounting information: 0/64 done

extracting archive '/var/lib/vz/template/cache/debian-8-turnkey-wordpress_14.2-1_amd64.tar.gz'
tar: ./var/spool/postfix/dev/random: Cannot mknod: Operation not permitted
tar: ./var/spool/postfix/dev/urandom: Cannot mknod: Operation not permitted
Total bytes read: 641136640 (612MiB, 141MiB/s)
tar: Exiting with failure status due to previous errors
Removing image: 1% complete...
...
Removing image: 100% complete...done.
TASK ERROR: command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- tar xpf /var/lib/vz/template/cache/debian-8-turnkey-wordpress_14.2-1_amd64.tar.gz --totals --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.*' '--xattrs-include=security.capability' '--warning=no-xattr-write' -C /var/lib/lxc/116/rootfs --skip-old-files --anchored --exclude './dev/*'' failed: exit code 2

Hat da jemand die selbe Erfahrung gemacht oder klappt das ohne Probleme?

Vielen Dank im Voraus!
 
Hallo liebe Forengemeinde,

ich habe heute zum ersten mal versucht einen LXC Container mit einem TurnKey Template zu erstellen, leider ohne Erfolg. Hab das natürlich auch mit mehreren Versuch ;)

Proxmox Version ist: pve-manager/4.4-15/7599e35a

Code:
/dev/rbd3
mke2fs 1.42.12 (29-Aug-2014)
Discarding device blocks: 4096/2097152 done
Creating filesystem with 2097152 4k blocks and 524288 inodes
Filesystem UUID: baf18ad1-b1aa-4e01-9703-9168e477c8ea
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 (32768 blocks): done
Multiple mount protection is enabled with update interval 5 seconds.
Writing superblocks and filesystem accounting information: 0/64 done

extracting archive '/var/lib/vz/template/cache/debian-8-turnkey-wordpress_14.2-1_amd64.tar.gz'
tar: ./var/spool/postfix/dev/random: Cannot mknod: Operation not permitted
tar: ./var/spool/postfix/dev/urandom: Cannot mknod: Operation not permitted
Total bytes read: 641136640 (612MiB, 141MiB/s)
tar: Exiting with failure status due to previous errors
Removing image: 1% complete...
...
Removing image: 100% complete...done.
TASK ERROR: command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- tar xpf /var/lib/vz/template/cache/debian-8-turnkey-wordpress_14.2-1_amd64.tar.gz --totals --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.*' '--xattrs-include=security.capability' '--warning=no-xattr-write' -C /var/lib/lxc/116/rootfs --skip-old-files --anchored --exclude './dev/*'' failed: exit code 2

Hat da jemand die selbe Erfahrung gemacht oder klappt das ohne Probleme?

Vielen Dank im Voraus!


Funktioniert, wenn "unprivileged" nicht gesetzt ist.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!