Rancher Desktop stuck on Initializing

[dgeiselmanMOO]

Actual Behavior

When loading Rancher for the first time, it is stuck on Initializing Rancher Desktop after running through all other startups

Steps to Reproduce

Install Rancher Desktop on Windows 10 machine and load the application. Runs through all startup

Result

Stuck on Initializing Rancher Desktop and will sit there for hours.

wsl.log
2024-06-24T12:46:29.571Z: Registered distributions: rancher-desktop,rancher-desktop-data
2024-06-24T12:46:30.557Z: Registered distributions: rancher-desktop,rancher-desktop-data
2024-06-24T12:46:31.476Z: Registered distributions: rancher-desktop,rancher-desktop-data
2024-06-24T12:46:32.335Z: Registered distributions: rancher-desktop,rancher-desktop-data
2024-06-24T12:46:32.335Z: data distro already registered
2024-06-24T12:46:49.064Z: Installing C:\Program Files\Rancher Desktop\resources\resources\linux\internal\trivy as /mnt/c/Program Files/Rancher Desktop/resources/resources/linux/internal/trivy into /usr/local/bin/trivy ...
2024-06-24T12:46:51.972Z: Installing C:\Program Files\Rancher Desktop\resources\resources\linux\internal\rancher-desktop-guestagent as /mnt/c/Program Files/Rancher Desktop/resources/resources/linux/internal/rancher-desktop-guestagent into /usr/local/bin//rancher-desktop-guestagent ...

wsl-init.log

�[1m�[32mOpenRC �[1m�[36m0.48�[m is starting up �[1m�[34mLinux 5.15.153.1-microsoft-standard-WSL2 (x86_64) [DOCKER]�[m

�[1m�[32m�[m /proc is already mounted�[K
�[1m�[32m�[m /run/openrc: creating directory�[K
�[1m�[32m�[m /run/lock: correcting mode�[K
�[1m�[32m�[m /run/lock: correcting owner�[K
�[1m�[32m�[m Caching service dependencies�[K ...
�[1m�[31m�[m /etc/fstab does not exist�[K
Service hwdrivers' needs non existent service dev'
[ ok ]
�[1m�[32m�[m Starting busybox crond�[K ...
[ ok ]
�[1m�[32m�[m Getting IP address for eth0�[K ...
[ ok ]
�[1m�[32m�[m Starting host-resolver�[K ...
[ ok ]
�[1m�[32m�[m Starting vtunnel-peer�[K ...
[ ok ]
�[1m�[32m*�[m Starting Rancher Desktop Guest Agent�[K ...
[ ok ]

wsl-exec.log

• /etc/fstab does not exist
  Service hwdrivers' needs non existent service dev'

• Caching service dependencies ... [ ok ]
  2024-06-24T12:47:32.575Z: Running: wsl.exe --distribution rancher-desktop --exec /usr/local/bin/wsl-service --ifnotstarted local start

• Starting local ... [ ok ]
  2024-06-24T12:47:33.255Z: Running: wsl.exe --distribution rancher-desktop --exec /sbin/rc-update --update

• /etc/fstab does not exist
  Service hwdrivers' needs non existent service dev'

• Caching service dependencies ... [ ok ]
  2024-06-24T12:47:33.932Z: Running: wsl.exe --distribution rancher-desktop --exec /usr/local/bin/wsl-service --ifnotstarted docker start

• Starting Rancher Desktop Docker Daemon ...

• supervise-daemon: Please increase the value of --respawn-period to more than 50 to avoid infinite respawning
  [ ok ]

Expected Behavior

Rancher loads and docker is running

Additional Information

No response

Rancher Desktop Version

1.11.1 and 1.14

Rancher Desktop K8s Version

Not using

Which container engine are you using?

moby (docker cli)

What operating system are you using?

Windows

Operating System / Build Version

Windows 10 Enterprise 22H2

What CPU architecture are you using?

x64

Linux only: what package format did you use to install Rancher Desktop?

None

Windows User Only

Trying to run on my local system to test applications being moved to docker/TKG

[Nino-K]

Are you behind a VPN?

[dgeiselmanMOO]

I am, but it is for running on my machine locally to test

[dgeiselmanMOO]

Disconnected from my VPN and tried to get it to run, it gets stuck on Initializing Rancher Desktop.

[Nino-K]

If you were using the version 1.11.1 you would need to enable the network tunnel. However, for our latest version 1.14.2 you should not have to do anything, even if you are behind a VPN things should just work as expected. Can you use the latest version if possible? I would also recommend doing a factory reset and trying it.

[dgeiselmanMOO]

Installed 1.14.2 and did a factory reset, still having the same issue.

[jny-gk]

Got the same issue with 1.16.0. Is there a solution yet?

[jandubois]

Can you zip up all the log files and send them to us? I can't spot any errors in the extracts shown above.