rancher-sandbox / rancher-desktop

Container Management and Kubernetes on the Desktop
https://rancherdesktop.io
Apache License 2.0
6.04k stars 285 forks source link

Stuck at "Initializing Rancher Desktop" #7805

Closed hrunting closed 5 days ago

hrunting commented 1 week ago

Actual Behavior

When I start Rancher Desktop, it goes through several steps and then the status bar says, "Initializing Rancher Desktop" and stays there without completing.

Steps to Reproduce

  1. Launch Rancher Desktop

Result

Application status bar stays at "Initializing Rancher Desktop" and interfaces like "Containers" and "Images" do not display anything useful because they are waiting for startup to complete.

Expected Behavior

Application works.

Additional Information

Application is installed for user only, not for all users on system. WSL2 was already installed with one distribution (Ubuntu). The "Enable Kubernetes" checkbox is UNCHECKED. The "Allow collection of anonymous statistics to help us improve Rancher Desktop" is unchecked.

In the background.log file, the following two lines repeat once each second (pid of process changes each time):

2024-11-24T16:36:35.013Z: Launching background process Win32 socket proxy. 2024-11-24T16:36:35.070Z: Background process Win32 socket proxy (pid 25456) exited with status 1 signal null

Rancher Desktop Version

1.16.0

Rancher Desktop K8s Version

v1.30.6

Which container engine are you using?

moby (docker cli)

What operating system are you using?

Windows

Operating System / Build Version

Windows 11 Pro 23H2

What CPU architecture are you using?

x64

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

N/A

Windows User Only

No

gunamata commented 6 days ago

@hrunting , Can you please share full application logs from your session?

hrunting commented 6 days ago

@gunamata, I can't anymore. I saw some notes in various forums of people having problems with Rancher if they previously had Podman Desktop installed. I had PD previously installed, but had uninstalled it and verified that the PD-related WSL distros had been unregistered. The notes in forums mentioned that rebooting reset some things, so I tried that and it appears to have worked. The logs I have on disk do not include the information from the problem period anymore.

jandubois commented 5 days ago

@hrunting Thanks for the info about Podman Desktop. I'm going to close this as not-reproducible for now.