This message was deleted.

Hi @colossal-ram-54386! Thank you for message 🙂 Do you mind telling a little bit more about your setup (OS, rancher-desktop version, etc.)? Also, have you already taken a look at the logs?

Yes, sorry. I'm currently on Windows 11 and am running rancher desktop version 1.9.0. I wasn't sure what logs to look at or what to look for (I'm quite new to rancher desktop). I thought maybe if I ask here, you could point me to what logs might contain the information I'm looking for :D

No worries 🙂 Could you please take a look at the "Troubleshooting" page and see if the "Enable debug mode" checkbox is checked?

It was not

Possibly restart the application just to be sure you get the debug output.

I'm looking through them

Hmmm... that's hard to tell. It depends on the actual issue. I usually sort them by file size and start with the biggest one.

Okay thanks

No, I don't think so. Are

2023-06-23T08:03:04.841Z: Background process Win32 socket proxy (pid 11100) exited with status 1 signal null
2023-06-23T08:03:04.842Z: Background process Win32 socket proxy will restart (process 11100 exited)
2023-06-23T08:03:05.849Z: Stopping exising Win32 socket proxy process (pid 11100)

the messages you're talking about?

Yes. Those are exactly the ones I'm talking about

I have them in my log several times as well. But at some point it got:

2023-06-23T08:03:05.850Z: Launching background process Win32 socket proxy.
2023-06-23T08:03:05.860Z: Launched background process Win32 socket proxy (pid 10748)
2023-06-23T08:03:31.198Z: Restarting Win32 socket proxy (pid 10748): ignoring restart, already alive

and the failures do no longer appear afterwards.

Same here

Okay... then I think it's fine.

How does your wsl-helper.log file look? Mine is full of

Error: could not listen on npipe:////./pipe/docker_engine: open //./pipe/docker_engine: Access is denied.

, but it stops after some line (and by some lines I mean like 2000 lines lol)

Oh... this message doesn't look like expected behavior. I don't have it in my log file.

We found something I guess

do you have any other WSL distros loaded to make suer WSL and the hypervisor feature are working?

I do

win11 required Control Flow Guard for the hypervisor to work (w10 didn't) and it's been causing issues out there

Not sure if it's important but this started happening after I tried podman desktop and podman (I closed rancher, opened podman and ran the podman machine). Podman desktop wasn't working well for me so I decided to go back to rancher, so I removed the podman machine, uninstalled podman and podman desktop and ran rancher again. That's when it stopped working

might want to check your docker contexts

I only have one and it's the default one. The endpoint is at npipe:////./pipe/docker_engine. It's the same as the one in the logs (there is a lot of these Access Denied errors connected with that endpoint)

and guessing you didn't install as admin. can never remember how each tool sets the DOCKER_HOST. spinning up my iwndows machine to look

@wide-mechanic-33041 You don't need admin for rancher desktop. The access denied is for another reason. I fixed it. I don't know why I didn't think to restart (my pc), but it fixed it. I'm guessing it got the access denied, because there were still some things left from podman desktop. Thanks for your help!

you don't but there is the privilaged-service component that helps with some of the networking in some cases. depends on how you install.