@vanes, thanks for posting your issue and thank you @Stefan_R for the fix. This was kinda troublesome for me as well, and had a hard time finding the cause.
Do we have any option to run PVE6 with a stable kernel instead of kernel which is still kinda in development?
Thanks for the info. I'm actually not worrying at all because of that folder, I'm just questioning why the PVE team decided that you must select a content type, when defining an NFS mount.
Alright, thanks for posting.
However, just to be sure, I just moved all NFS mounts to the proxmox host, and 'bind mounted' all of them to the individual lxc's.
I find it strange that Proxmox forces me to select one of the 'content types (see screenshot below) An alternative is a systemd mount...
I do however have mounted NFS resources from within my containers. I read somewhere this is not advised by the proxmox team. So I should make use of bind mounts. Is there any evidence NFS mounts have a relation with this issue?
Same problem here:
kworker 100%:
startup lxc failing:
The topic title says "solved", where can I find the details how to resolve this issue on my system?
pveversion -V:
root@server:~# uname -a
Linux server 4.15.18-13-pve #1 SMP PVE 4.15.18-37 (Sat, 13 Apr 2019 21:09:15 +0200) x86_64...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.