This message was deleted.

I uninstalled and reverted back to an earlier version (I went to 1.5.1) https://github.com/rancher-sandbox/rancher-desktop/issues/3288

Thanks a lot Jason! By the way, how to properly uninstall my current version and install a previous one, as you suggested, on a macOS? Should I just Factory Reset the current one and download and install another version?

Yep, I did the factory reset and installed the older one over it

I have tried making 1.6.1 run on ventura (intel) and it seems that the whole lima vm is hanging .. I’m unable to get at shell on the vm .. it just hangs..

yep, that's been my experience as well

Do we know if anybody is actively looking into the issue? .. I’m so very sad when rd is not working 😉

I can confirm that @calm-sugar-3169 and I are actively looking into this issue.

I just had the chance to test now, and using Kubernetes v1.20.15 is working fine. I had to do a Factory Reset though. Only going into Preferences and changing the Kubernetes version and restarting the application didn’t work.

well.. I did a complete removal of rd and installed anew, selecting v1.20.15 at installation, and it still won’t start just keeps “waiting for services” .. :/

In my experience it is working as long as you use it with kubernetes 1.23 or earlier. I've seen some reports that claim it doesn't, but I haven't been able to verify that. Unfortunately I still don't understand the root cause. 😞

Having the same issue since upgrading to macOS 13 on an M1 chip Macbook Pro 🙂 My workaround until i read this thread was factory resetting rd every day i start working 😢

I suspect your first factory reset didn't work because I think it does not shut down the app properly. You need to quit Rancher Desktop from the notification icon before starting it again. Or perform the factory reset 2 or 3 times in a row. You can tell when the UI comes back up in less than 10s, then the app was not stopped, and the new UI will still be talking to the old engine

hmm.. okay thanks for the feedback! 🙂 i will have an eye on that next time 👍

I found that if you wipe the Kubernetes installation during boot, it will continue to work (but you lose all images and workloads on each restart). You can automate that with an

override.yaml

file (in

~/Library/Application\ Support/rancher-desktop/lima/_config/override.yaml

):

provision:
- mode: system
  script: |
    #!/bin/sh
    set -o errexit -o nounset -o xtrace
    rm -rf /var/lib/rancher

Thank you for investigating the error 🙂👍 think i might downgrade to v1.5.1 then until fixed 🙂 thanks!

Even more than the fact that you're working on it, I greatly appreciate the updates here to let us know what's going on. Kudos for that!

I’m having a possibly unrelated issue as well. I need local kubernetes and use rancher in docker only, without kubernetes, and installed microk8s + multipass as an alternative. However, sometimes when I start rancher 1.6.1 it breaks microk8s. the

microk8s status

command no longer detects it as being installed and recommends I run the install command, even though multipass shows that the vm is running. I haven’t investigated too deeply, but suspect that starting rancher breaks microk8s networking somehow.

@glamorous-application-56494 This sounds unrelated, so please start your own thread, or file a Github issues with more details. The only thing I can think off would be a port conflict. I don't know how microk8s works, which ports and sockets it may need to forward to the host.

Thank you. I’ll look into possible port conflicts and raise a separate thread/issue if necessary. I’ve also downgraded to 1.5.1 and it seems stable so far.

We are testing a release candidate for 1.6.2 with a fix for the Ventura issue right now, and if testing passes before the end of the day, we will release it. Otherwise we may need to delay to Monday due to a policy of not releasing on the day before the weekend or public holidays.

Just downloaded v1.6.2 from the github release page, tested it and it works fine! thanks a lot for the quick fix 🙂👍