[SOLVED] Restore CT from Proxmox 4.4-18 to proxmox 5.3-12

[nico las]

Hello everyone,

I'm doing a CT migration on proxmox, but I'm stuck. I am doing a server migration and a proxmox update to a new version. I have my old server under Proxmox 4.4-18 and my new server under proxmox 5.3-12. Below are the steps that I realized.

- I stopped my CT 106 on my old server
- I made a backup vzdump in tar.gz of my CT
- I got my tar.gz dump archive with Filzilla
- I have activated the vzdump files in the local of my new server
- I send on my new server the .log and .tar.gz in /var/lib/vz/dump
- On the web interface proxmox I then selected local> content> then the archive of my CT> click on Restore
- I then have an error message

Virtual Environment 5.3-12

You are logged in as 'root@pam'
()

Task viewer: CT 100 - Restore

OutputStatus

Stop
Formatting '/var/lib/vz/images/100/vm-100-disk-0.raw', fmt=raw size=34359738368
mke2fs 1.43.4 (31-Jan-2017)
Discarding device blocks: 4096/8388608 done
Creating filesystem with 8388608 4k blocks and 2097152 inodes
Filesystem UUID: 18871912-d3d4-4a71-8183-ab8ef6b6cbea
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624

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

extracting archive '/var/lib/vz/dump/vzdump-lxc-106-2019_03_21-06_42_25.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: 2126653440 (2.0GiB, 140MiB/s)
tar: Exiting with failure status due to previous errors
TASK ERROR: unable to restore CT 100 - 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/100/rootfs --skip-old-files --anchored --exclude './dev/*'' failed: exit code 2

 

[dcsapak]

the backup contains device nodes (/dev/random), that cannot be restored as an unprivileged container => restore as privileged

 

[nico las]

Hello, thanks for your quick reply. Could you tell me more please, i'm not an expert yet

Can I restore as privileged directly from the web interface ? I don't see this option sorry.

 

[nico las]

I also found your other answer on another post but I do not know how to do it, would you have a solution please?
"The original container was privileged, and /dev/random cannot be create on unprivileged containers (it is simply not permitted)."

 

[dcsapak]

Can I restore as privileged directly from the web interface ? I don't see this option sorry.

yes, just uncheck 'unprivilged'

 

[nico las]

Thanks for your help !
the checkbox was gray I did not think I could change it. A big thank you for your help, you are great.

 

[zonelock]

yes, just uncheck 'unprivilged'

i have this problems, where i can get for 'unprivilged' ?

 

[nico las]

When you select a CT > Options > unprivilged

 

[zonelock]

big thks, solved