This message was deleted.

│ │ │ │ │ │ └─rancher-desktop │ │ │ │ │ │ ├─limactl shell --workdir=. 0 sudo /sbin/rc-update --update │ │ │ │ │ │ │ ├─ssh -F /dev/null -o IdentityFile="/home/iocc/.local/share/rancher-desktop/lima/_config/user" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o ... │ │ │ │ │ │ │ └─9*[{limactl}] │ │ │ │ │ │ ├─rancher-desktop │ │ │ │ │ │ │ └─rancher-desktop │ │ │ │ │ │ │ └─21*[{rancher-desktop}] │ │ │ │ │ │ ├─rancher-desktop │ │ │ │ │ │ │ └─rancher-desktop │ │ │ │ │ │ ├─rancher-desktop │ │ │ │ │ │ │ └─5*[{rancher-desktop}] │ │ │ │ │ │ ├─rancher-desktop │ │ │ │ │ │ │ └─22*[{rancher-desktop}] │ │ │ │ │ │ ├─zsh -i -l -c printf "\012Rancher Desktop Diagnostics PATH:%s\012" "$PATH" │ │ │ │ │ │ └─29*[{rancher-desktop}]

Hi! Thank you for reporting the issue here. Have you already tried to do a factory reset?

U're welcome. No I havent but will it reset other k8s contexts than rancher-desktop?

The documentation https://docs.rancherdesktop.io/ui/troubleshooting#factory-reset doesn't mention anything about it. I tried it on my env. I created a new context:

╰─$ kubectl config set-context test
Context "test" created.

And did a factory reset. Afterwards I checked the contexts again and

test

was still available:

╰─$ kubectl config get-contexts    
CURRENT   NAME              CLUSTER           AUTHINFO          NAMESPACE
          default           default           default           
*         rancher-desktop   rancher-desktop   rancher-desktop   
          test

But if you need to be really sure about it, I would rather suggest to just open an issue on the tracker (https://github.com/rancher-sandbox/rancher-desktop/issues) for now. I'm sorry.

Yes, it seems to not have touched .kube/config. Now its up. It kinda worked but I have two hung zsh that are using 100% cpu. Its always like this... 1 failed but it doesnt tell which one.

Thank you!