[SOLVED] LCX: reviving containers give nogroup nobody

[Sxilderik]

Hello

I accidentally removed my containers, or so I thought, when I realized the disks were still available.

So I created a new container (208) with the same specs as the old one (108), then edited the 208.conf file to replace disk location with the 108 one.

It doesn’t work. Can’t log in.

I used pct enter 208 and found out that all the rights were 65534:65534 (nobody:nogroup).

I’m stuck. I’ve read countless posts, learnt many things but none was exactly relevant to the situation I put myself in.

my original 208.conf file:

arch: amd64
cores: 2
hostname: <some hostname>
memory: 4096
net0: name=eth0,bridge=vmbr0,gw=172.16.1.254,hwaddr=<hwaddr>,ip=172.16.1.169/23,ip6=auto,type=veth
ostype: centos
rootfs: local-lvm:vm-208-disk-0,size=64G
swap: 4096
unprivileged: 1

my modified 208.conf file :

arch: amd64
cores: 2
hostname: <some hostname>
memory: 4096
net0: name=eth0,bridge=vmbr0,gw=172.16.1.254,hwaddr=<hwaddr>,ip=172.16.1.169/23,ip6=auto,type=veth
ostype: centos
rootfs: local-lvm:vm-108-disk-1,size=64G
swap: 4096
unprivileged: 1

Result of pct enter 208:

root@makemake:/etc/pve/lxc# pct enter 208
bash: /root/.bashrc: Permission denied
bash-4.2# ls -al
total 76
dr-xr-xr-x  19 65534 65534  4096 Jun 27 15:16 .
dr-xr-xr-x  19 65534 65534  4096 Jun 27 15:16 ..
-rw-r--r--   1 65534 65534     0 Apr 25  2018 .autorelabel
lrwxrwxrwx   1 65534 65534     7 Aug  7  2018 bin -> usr/bin
dr-xr-xr-x   3 65534 65534  4096 Oct 26  2018 boot
drwxr-xr-x   6 root  root    460 Jun 27 15:16 dev
drwxr-xr-x  81 65534 65534  4096 Jun 27 15:16 etc
-rw-r--r--   1 root  root      0 Jun 27 15:16 fastboot
drwxr-xr-x   3 65534 65534  4096 Apr 11  2018 home
lrwxrwxrwx   1 65534 65534     7 Aug  7  2018 lib -> usr/lib
lrwxrwxrwx   1 65534 65534     9 Aug  7  2018 lib64 -> usr/lib64
drwx------   2 65534 65534 16384 Apr 25  2018 lost+found
drwxr-xr-x   2 65534 65534  4096 Apr 11  2018 media
drwxr-xr-x   2 65534 65534  4096 Apr 11  2018 mnt
drwxr-xr-x   4 65534 65534  4096 Jan 29 17:43 opt
dr-xr-xr-x 261 65534 65534     0 Jun 27 15:16 proc
-rw-------   1 65534 65534  1024 Oct 23  2018 .rnd
dr-xr-x---   5 65534 65534  4096 Jan 29 17:45 root
drwxr-xr-x  20 root  root    440 Jun 27 15:19 run
lrwxrwxrwx   1 65534 65534     8 Aug  7  2018 sbin -> usr/sbin
drwxr-xr-x   2 65534 65534  4096 Dec 12  2017 selinux
drwxr-xr-x   2 65534 65534  4096 Apr 11  2018 srv
dr-xr-xr-x  13 65534 65534     0 Jun 13 14:40 sys
drwxrwxrwt  15 65534 65534  4096 Jun 27 15:16 tmp
drwxr-xr-x  14 65534 65534  4096 Dec 20  2018 usr
drwxr-xr-x  19 65534 65534  4096 Oct 23  2018 var
bash-4.2#

My disks


Thanks for helping me out!

 

[Stoiko Ivanov]

unprivileged: 1

I guess that the original container was not unprivileged
You could try removing this line and trying again.

But it might be even better to mount the 108 disk and syncing stuff to the appropriate disk for 208 (if your storage is lvm-thin you could simply use `dd` for this) - since PVE expects the disks to be named vm-$vmid-disk-$n for a guest with the id $vmid

hope this helps!

 

[Sxilderik]

Thanks, setting unprivileged to 0 worked !
I can’t remember why I created that container as privileged in the first place, though.

I now have another problem but I’ll start a new thread for that which I solved by myself

Thanks again

 

[soporteit]

I guess that the original container was not unprivileged
You could try removing this line and trying again.

But it might be even better to mount the 108 disk and syncing stuff to the appropriate disk for 208 (if your storage is lvm-thin you could simply use `dd` for this) - since PVE expects the disks to be named vm-$vmid-disk-$n for a guest with the id $vmid

hope this helps!

I love you <3