PVE 7 won't start CentOS 7 container

Vasilij Lebedinskij

Active Member
Jan 30, 2016
59
2
28
36
I know there was a warning but I thought lxc will start and I read here that one can start lxc, chroot inside and update dist but I can't - lxc starts with warning and ram consumption shows near 1mb with no life signs no console and I can't pct enter it... Is there any chances to get it working or I have to move my container to pve 6 environment?
 

oguz

Proxmox Staff Member
Staff member
Nov 19, 2018
3,884
476
88
hi,

centos 7 container works with PVE 7 despite the warning.

what is your pveversion -v output saying? and what about your container configuration pct config CTID?

please sure that you have the latest updates available with apt update && apt dist-upgrade
 

Vasilij Lebedinskij

Active Member
Jan 30, 2016
59
2
28
36
Here you go
Code:
proxmox-ve: 7.0-2 (running kernel: 5.11.22-5-pve)
pve-manager: 7.0-13 (running version: 7.0-13/7aa7e488)
pve-kernel-helper: 7.1-2
pve-kernel-5.11: 7.0-8
pve-kernel-5.4: 6.4-5
pve-kernel-5.3: 6.1-6
pve-kernel-5.0: 6.0-11
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-4-pve: 5.11.22-9
pve-kernel-5.4.128-1-pve: 5.4.128-2
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.78-1-pve: 5.4.78-1
pve-kernel-5.4.60-1-pve: 5.4.60-2
pve-kernel-4.15: 5.4-6
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.13-1-pve: 5.3.13-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.21-4-pve: 5.0.21-9
pve-kernel-5.0.18-1-pve: 5.0.18-3
pve-kernel-5.0.15-1-pve: 5.0.15-1
pve-kernel-4.15.18-18-pve: 4.15.18-44
pve-kernel-4.15.18-12-pve: 4.15.18-36
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve1
libproxmox-acme-perl: 1.3.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-10
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-3
libpve-storage-perl: 7.0-12
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.11-1
proxmox-backup-file-restore: 2.0.11-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.0-10
pve-docs: 7.0-5
pve-edk2-firmware: 3.20210831-1
pve-firewall: 4.2-3
pve-firmware: 3.3-2
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-4
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-16
smartmontools: 7.2-pve2
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1

And CT config
Code:
arch: amd64
cores: 4
hostname: issabel
memory: 1024
net0: name=eth0,bridge=vmbr0,gw=172.16.100.1,hwaddr=A6:46:41:3F:9F:67,ip=172.16.100.10/24,type=veth
onboot: 1
ostype: centos
parent: afterupgrade
rootfs: local-zfs:subvol-102-disk-0,size=38G
searchdomain: pl-group.ru
swap: 1024
lxc.mount.entry: /rpool/certs etc/letsencrypt/archive none rw,bind 0.0
 

Vasilij Lebedinskij

Active Member
Jan 30, 2016
59
2
28
36
And I've noticed today that my old CT with ubuntu 14.04 won't start as well. 1mb of ram usage and nothing else. However I can't pct enter these containers but nothing works in their shell....
 

oguz

Proxmox Staff Member
Staff member
Nov 19, 2018
3,884
476
88
did you use our templates or did you download them from somewhere else? i'm asking because we don't have an ubuntu 14.04 container template available :)

you can download our official templates with the pveam tool or using the GUI Storage (for example "local") -> CT Templates -> Templates and in the popup menu you should be able to choose and download our official templates.
 

Vasilij Lebedinskij

Active Member
Jan 30, 2016
59
2
28
36
did you use our templates or did you download them from somewhere else? i'm asking because we don't have an ubuntu 14.04 container template available :)

you can download our official templates with the pveam tool or using the GUI Storage (for example "local") -> CT Templates -> Templates and in the popup menu you should be able to choose and download our official templates.
Its old CT from PVE v4 time I think
 

Vasilij Lebedinskij

Active Member
Jan 30, 2016
59
2
28
36
I use only official PVE templates. I've downloaded latest CentOS 7 template and it starts with no services available inside not even network.
 

oguz

Proxmox Staff Member
Staff member
Nov 19, 2018
3,884
476
88
I use only official PVE templates. I've downloaded latest CentOS 7 template and it starts with no services available inside not even network.
if you run ifup eth0 does networking come up? (/dev/stderr: Permission denied can be ignored)
 

Vasilij Lebedinskij

Active Member
Jan 30, 2016
59
2
28
36
Nope
Code:
Determining IP information for eth0... done.
./network-functions: line 286: cd: /var/run/netreport: No such file or directory
 

oguz

Proxmox Staff Member
Staff member
Nov 19, 2018
3,884
476
88
Nope
Code:
Determining IP information for eth0... done.
./network-functions: line 286: cd: /var/run/netreport: No such file or directory
ip a doesn't show IP address regardless? works here...
 

Vasilij Lebedinskij

Active Member
Jan 30, 2016
59
2
28
36
If I try in my old CT with CentOS 7 I get this
Code:
[root@issabel ~]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0@if71: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether a6:46:41:3f:9f:67 brd ff:ff:ff:ff:ff:ff link-netnsid 0
[root@issabel ~]# ifup eth0
ERROR     : [ipv6_wait_tentative] Duplicate Address Detection: Duplicate addresses detected
ERROR     : [ipv6_wait_tentative] Duplicate Address Detection: Please, fix your network configuration
./network-functions: line 286: cd: /var/run/netreport: No such file or directory
[root@issabel ~]# yum update
error: rpmdb: BDB0113 Thread/process 25740/139827402192704 failed: BDB1507 Thread died in Berkeley DB library
error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db5 -  (-30973)
error: cannot open Packages database in /var/lib/rpm
CRITICAL:yum.main:

Error: rpmdb open failed
 

oguz

Proxmox Staff Member
Staff member
Nov 19, 2018
3,884
476
88
could you please upgrade your packages on the node, try creating centos 7 container from template and run ifup eth0 inside it and check if networking works?
 

oguz

Proxmox Staff Member
Staff member
Nov 19, 2018
3,884
476
88
it works here on a freshly installed PVE 7, upgraded to the latest available package versions:

Code:
[root@centos-7 ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0@if4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 42:0d:bc:49:14:82 brd ff:ff:ff:ff:ff:ff link-netnsid 0
[root@centos-7 ~]# ifup eth0
/etc/init.d/functions: line 63: /dev/stderr: Permission denied
/etc/init.d/functions: line 63: /dev/stderr: Permission denied
/etc/init.d/functions: line 63: /dev/stderr: Permission denied
/etc/init.d/functions: line 63: /dev/stderr: Permission denied
/etc/init.d/functions: line 63: /dev/stderr: Permission denied
./network-functions: line 286: cd: /var/run/netreport: No such file or directory
[root@centos-7 ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 42:0d:bc:49:14:82 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 192.168.22.212/24 brd 192.168.22.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::400d:bcff:fe49:1482/64 scope link 
       valid_lft forever preferred_lft forever

notice that the IP address is assigned regardless of the error message you've posted here.

here's the container configuration:
Code:
root@pve:~# pct config 100
arch: amd64
cores: 1
features: nesting=1
hostname: centos-7
memory: 512
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=22:AD:3C:42:11:22,ip=dhcp,type=veth
ostype: centos
rootfs: local:100/vm-100-disk-0.raw,size=8G
swap: 512
unprivileged: 1

the template i'm using is: centos-7-default_20190926_amd64.tar.xz from our templates repository.
it also works with static IPv4 address.

if the above doesn't work for you, please post your container configuration...

also be aware of cgroup version compatibility issues with centos 7 [0]

[0]: https://pve.proxmox.com/pve-docs/chapter-pct.html#pct_cgroup_compat
 

ales

New Member
Jul 26, 2020
9
1
3
44
Same problem here.
PVE 7 with latest packages from no-subscription repository.
centos-7-default_20190926_amd64.tar.xz template

Code:
root@proxmox:~# pct config 10001
arch: amd64
cores: 2
features: nesting=1
hostname: centosette
memory: 2048
net0: name=eth0,bridge=vmbr1,firewall=1,gw=192.168.122.1,hwaddr=D6:47:54:27:9E:12,ip=192.168.122.200/24,type=veth
ostype: centos
rootfs: local-zfs:subvol-10001-disk-0,size=18G
swap: 0
unprivileged: 1

Connecting to the CT using pct enter works, I can activate the network with ifup eth0, but the console using the web interface is unavailable, and shutdown/reboot doesn't work as well.
 

ales

New Member
Jul 26, 2020
9
1
3
44
Ok. I can confirm that it is related to CGroupv2.

Oct 22 14:32:16 proxmox pve-lxc-hook-lxc-pre-start[291859]: CT 10001 does not support running in a pure cgroupv2 environment

Already discussed here: https://forum.proxmox.com/threads/unified-cgroup-v2-layout-upgrade-warning-pve-6-4-to-7-0.92459/

My workaround:
- gain access to the CT with pct enter <CTID>
- enable the network with ifup eth0
- download this yum repository: https://copr.fedorainfracloud.org/coprs/jsynacek/systemd-backports-for-centos-7/
- curl -o /etc/yum.repos.d/jsynacek-systemd-backports-for-centos-7-epel-7.repo https://copr.fedorainfracloud.org/coprs/jsynacek/systemd-backports-for-centos-7/repo/epel-7/jsynacek-systemd-backports-for-centos-7-epel-7.repo
- issue yum update
- exit from the CT
- stop the CT with pct stop <CTID>
- start the CT normally
 
  • Like
Reactions: oguz

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 your own in 60 seconds.

Buy now!