Recent content by Vasilij Lebedinskij

Its not Proxmox problem its old CentOS without official updates from devs

Unfortunately I don't have this service on this host

Same here PVE 7.1.9 I can't start unprivileged CTs even newly created won't start. Fstab on host is default and in ct is empty.

I don't like docker either but this particular service is available in docker only... I've figured out that problem is in aufs module which is no longer available in PVE kernel.

I think I've found general error in syslog Dec 24 03:40:52 unms-srv modprobe[153]: modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/5.11.22-5-pve/modules.dep.bin' Dec 24 03:40:52 unms-srv modprobe[153]: modprobe: FATAL: Module overlay not...

Hello! Recently I've updated one of my servers to PVE 7 and encountered a problem with on of LXC containers on it. There was a docker service UNMS (management software for network equipment) and it stoped working. In syslog I've found error failed to start daemon: error initializing...

This it new container from most recent CentOS 7 template after updating PVE and network doesn't work

If I try in my old CT with CentOS 7 I get this [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...

Its new clean CentOS 7 CT

Nope Determining IP information for eth0... done. ./network-functions: line 286: cd: /var/run/netreport: No such file or directory

I use only official PVE templates. I've downloaded latest CentOS 7 template and it starts with no services available inside not even network.

Its old CT from PVE v4 time I think

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....

Here you go 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...

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...