Closed swoutch closed 1 year ago
Oct 12 08:03:16 linux.0e9675.com k3s[199561]: E1012 08:03:16.823817 199561 kubelet.go:1378] "Failed to start ContainerManager" err="open /proc/sys/kernel/panic: permission denied"
What sort of host are you running this on? Is this some sort of VPS where you don't have full root access to the underlying node? There's no other reason that k3s shouldn't have access to this.
What sort of host are you running this on? Is this some sort of VPS where you don't have full root access to the underlying node?
I indeed run it on a VPS, virtualized with openVZ. I thought I had full root access but I will check with the support.
Thanks for your help!
In your opinion, the issue is not related to modprobe not finding the br_netfilter and overlay kernel modules? (first lines of the logs)
No, those are not fatal errors. You're probably not going to be able to use Kubernetes on a VPS that doesn't give you real root on the node.
Environmental Info: K3s Version:
Node(s) CPU architecture, OS, and Version:
Cluster Configuration: Single node
Describe the bug: The node is stuck in
NotReady
state:The k3s service keeps restarting:
Steps To Reproduce:
Expected behavior: The node should be ready and the k3s service should not fail to start
Actual behavior: The node is never ready. The k3s service fails to start, and systemd keeps restarting it.
Additional context / logs: Here are the full logs: