k3s node not read, cni plugin not initialized #8803
maciejklimek
started this conversation in
General
Replies: 1 comment 1 reply
-
|
Wait for flannel to start. If the message doesn't go away within a few seconds, check for other warnings or errors in the logs. You didn't open this as an issue so we're missing all the info the issue template would normally ask for, but can you confirm that you haven't disabled flannel by setting --flannel-backend=none? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I have a problem with getting the server node to start up after k3s installation.
kubectl describe nodegives a clue :container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initializedAny ideas how to tackle this?
Beta Was this translation helpful? Give feedback.
All reactions