mook-as
commented
1 day ago Rancher Desktop is generally expected to run as a normal user (there's way too much code dealing with making sure WSL is installed correctly for that).
Would you be able to turn on extra logging and then attaching the logs to this issue, so we can see where it's breaking?
(I'm assuming you're not running Windows 10 pro on macOS, though)
Actual Behavior
When you launch Rancher it will go through several stages on boot up. The last of which is "Initialising Rancher Desktop". Rancher then hangs on this stage indefinitely. It is unstable until it is finished which means those affected are unable to run containers locally.
WSLU had been identified as a potential cause, however this behaviour is present even after WSLU is shutdown. Currently the only fix we have is to run as local admin, however we not always able to have admin access in our computers. Can you please suggest?
Steps to Reproduce
Initialise Rancher as normal user
Result
Always stuck on "Initializing Rancher Desktop" phase.
Expected Behavior
We expect that to open Rancher with normal user
Additional Information
No response
Rancher Desktop Version
latest
Rancher Desktop K8s Version
latest
Which container engine are you using?
containerd (nerdctl)
What operating system are you using?
macOS
Operating System / Build Version
Windows 10 pro
What CPU architecture are you using?
x64
Linux only: what package format did you use to install Rancher Desktop?
None
Windows User Only
No response