This message was deleted.

im on windows, latest version of rancher desktop (v1.7.0)

Hmm, odd; I see this in the log:

"kubelet exited: failed to run Kubelet: validate service connection: CRI v1 runtime API is not implemented for endpoint \"unix:///run/cri-dockerd.sock\": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService"

That's weird because I thought we shipped our own

cri-dockerd

to avoid those issues. Can you try using the

containerd

container engine to see if it changes anything? (Not as a fix/workaround, but more as a troubleshooting step.)