This message was deleted.

a guess: something is running before rancher desktop is fully up.

Yes this is what I think too. However, I am not doing something other than starting rancher desktop and k3s is started by rancher.

Those should be harmless log lines (they are only visible because debug logging is turned on); there shouldn't be any issues from them, as it should be retrying and succeeding later.

I’ve got the exact same problem like you said a few restarts does this trick but this can be really really annoying!

@proud-jewelry-46860 Well, it depends, right? Eventually you should get the log entry "2024/05/03 142406 [DEBUG] kubernetes: loaded kubeconfig /etc/rancher/k3s/k3s.yaml" printed and then kubernetes should start up. This does not happen for me. That message is spamming until a restart of my laptop and kubectl is not able to contact k3s, PS C:\Users\patrik> kubectl get svc E0503 153628.447676 35492 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:6443/api?timeout=32s": read tcp 127.0.0.162088 >127.0.0.16443: wsarecv: An existing connection was forcibly closed by the remote host. E0503 153631.457201 35492 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:6443/api?timeout=32s": read tcp 127.0.0.162093 >127.0.0.16443: wsarecv: An existing connection was forcibly closed by the remote host. E0503 153634.478397 35492 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:6443/api?timeout=32s": read tcp 127.0.0.162096 >127.0.0.16443: wsarecv: An existing connection was forcibly closed by the remote host. E0503 153637.488751 35492 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:6443/api?timeout=32s": read tcp 127.0.0.162100 >127.0.0.16443: wsarecv: An existing connection was forcibly closed by the remote host. E0503 153640.495523 35492 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:6443/api?timeout=32s": read tcp 127.0.0.162104 >127.0.0.16443: wsarecv: An existing connection was forcibly closed by the remote host. Unable to connect to the server: read tcp 127.0.0.162104 >127.0.0.16443: wsarecv: An existing connection was forcibly closed by the remote host. PS C:\Users\patrik> Presumably, the .kubeconfig file is stored somewhere else on my laptop and the guest agent needs to load the file before being able to start up. However, this does not seem to happen all the time.