I've just installed proxmox under WSL (latest version) and it all seems to be running fine, except for one rather critical component: I can't run LXC containers.
When I run a container I see:
Running lxc-start -n 100 -F -lDEBUG -o lxc-100.log gives (I've had to chop out some of the INFO...
I am facing problems starting all of our containers on a pve node after dist-upgrade and reboot.
All containers fail to start, VMs are coming up without problems.
It seems to boil down to a lxcfs / FUSE problem -- full messages attached.
Starting on console reveals:
# pct start...
I wanted to know if anyone has ever encountered the following problem:
2020-11-29T04:37:30.054129+01:00 hv18 systemd: lxcfs.service: Main process exited, code=killed, status=11/SEGV
2020-11-29T04:37:30.094752+01:00 hv18 systemd: lxcfs.service...
How to restart lxcfs, or, rather, how to resurrect /proc on running containers?
If lxcfs gets restarted by some or other reason all the CT's get choked:
# ps awuxf
Error: /proc must be mounted
To mount /proc at boot you need an /etc/fstab line like:
proc /proc proc defaults
I've noticed that lxcfs has virtualized the /sys/devices/system/cpu/online dir since lxcfs version 3.1.2, but it's not working for proxmox LXC:
After upgrade the proxmox, I saw the lxcfs version has upgrade to 4.0.1, but it seems not working:
LXCfs finaly has the per-container loadavg!
I wonder how long it will take to get to the Proxmox...