This message was deleted.

Anything useful in the Logs when you go through the Troubleshooting section? maybe in background or k3s that might indicate the issue?

Hey @wide-mechanic-33041 thanks for helping. Looks like both were collecting logs over the weekend. The background file has just a ton of these:

2022-06-24T18:45:57.298Z: Launching background process Win32 socket proxy.
2022-06-24T18:45:58.223Z: Background process Credentials Helper Host Proxy exited with status 1 signal null

and the k3s file, in terms of errors has this sort of thing

time="2022-06-24T18:47:19Z" level=info msg="Connecting to proxy" url="<wss://127.0.0.1:6443/v1-k3s/connect>"
time="2022-06-24T18:47:19Z" level=error msg="Failed to connect to proxy" error="websocket: bad handshake"
time="2022-06-24T18:47:19Z" level=error msg="Remotedialer proxy error" error="websocket: bad handshake"

I zipped my logs folder and attached here

i have seen those errors when i have env vars configured in my WSL environment. I don’t believe I see them when running without an http_proxy, but I have other issues in those scenarios.

is there anything i can do to try to clean up or reset my WSL environment so that Rancher works correctly? i haven't been playing with my WSL in any meaningful way

so Rancher doesn’t use Ubuntu?

so it's not actually related to the WSL integration at all? That's where i had the docker daemon running and containers and I had the checkbox checked for wsl integration (back when it actaully worked)

so were you using RD at all? Or were you running docker-engine in your Ubnt?

basically i would just install RD, let it do its thing to install of the dependencies it needs, open it, and then run a dotnet cake command (wrapping around a docker-compose command) that would setup our testing infrastructure. I could run that command on either windows cmd line or in ubuntu. i think i started doing everything in ubuntu because thats where i could manually install the docker engine without docker desktop since we cant use that

k so the containers were running in alpine and not in your ubuntu. you could docker ps them sure, but they were not “local”

gothca i see that now so the integration is just for exposure to ubuntu

only hits i am finding for that error points at proxy configs in your distro. So you are sure that you don’t have any http_proxy like env statements anywhere in rancher-desktop distro?

where would i be able to find that proxy config if any exists?

rdctl shell

to get into your Alpine distro and then

env

should show your environ

nope no http_proxy variables setup in env:

/mnt/c/Windows/System32 # env
USER=root
SHLVL=1
HOME=/root
WSL_DISTRO_NAME=rancher-desktop
LOGNAME=root
WSL_INTEROP=/run/WSL/4679_interop
NAME=jbaum-w02093
TERM=xterm-256color
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/wsl/lib:/mnt/c/Program Files/WindowsApps/Microsoft.PowerShell_7.2.5.0_x64__8wekyb3d8bbwe:/mnt/c/Program Files/Eclipse Foundation/jdk-8.0.302.8-hotspot/bin:/mnt/c/Windows/system32:/mnt/c/Windows:/mnt/c/Windows/System32/Wbem:/mnt/c/Windows/System32/WindowsPowerShell/v1.0/:/mnt/c/Windows/System32/OpenSSH/:/mnt/c/Program Files/Intel/WiFi/bin/:/mnt/c/Program Files/Common Files/Intel/WirelessCommon/:/mnt/c/Users/j.baum/AppData/Roaming/nvm:/mnt/c/Program Files/nodejs:/mnt/c/Program Files/Amazon/AWSCLIV2/:/mnt/c/Program Files/dotnet/:/mnt/c/Program Files (x86)/Microsoft SQL Server/150/DTS/Binn/:/mnt/c/Program Files/Microsoft SQL Server/130/Tools/Binn/:/mnt/c/Program Files/Microsoft SQL Server/Client SDK/ODBC/170/Tools/Binn/:/mnt/c/Program Files/Azure Data Studio/bin:/mnt/c/Program Files/nodejs/:/mnt/c/Program Files/Git/cmd:/mnt/c/Program Files/Microsoft SQL Server/150/Tools/Binn/:/mnt/c/Program Files (x86)/dotnet/:/mnt/c/Users/j.baum/scoop/shims:/mnt/c/Users/j.baum/.windows-build-tools/python27/:/mnt/c/Users/j.baum/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/j.baum/AppData/Roaming/npm:/mnt/c/Users/j.baum/AppData/Local/Programs/Microsoft VS Code/bin:/mnt/c/Users/j.baum/.dotnet/tools:/mnt/c/Program Files/Vault:/mnt/c/Program Files/MySQL/MySQL Workbench 6.2 CE:/mnt/c/Users/j.baum/Documents/Bats:/mnt/c/Program Files (x86)/NuGet:/mnt/c/Program Files (x86)/Android/android-sdk/platform-tools:/mnt/c/Program Files (x86)/Android/android-sdk/tools:/mnt/c/Program Files (x86)/Android/android-sdk/tools/bin:/mnt/c/Program Files/ChromeDriver:/mnt/c/DkSource/~/.tfenv/bin:/mnt/c/Users/j.baum/.dotnet/tools:/mnt/c/Users/j.baum/.dotnet/tools:/mnt/c/Users/j.baum/AppData/Local/Programs/Rancher Desktop/resources/resources/win32/bin:/mnt/c/Users/j.baum/AppData/Local/Programs/Rancher Desktop/resources/resources/linux/bin
LANG=en_US.UTF-8
SHELL=/bin/sh
PWD=/mnt/c/Windows/System32
HOSTTYPE=x86_64
WSLENV=

hmm head scratcher for me then. Probably need the rancher crew to lean in on their thoughts.

Hello - i never received any help from Rancher experts on this issue. This still exists for me. Does anyone from the Rancher team have time to help me. I've uninstalled, deleted everything, unregistered all WSL rancher distros, and reinstalled Rancher desktop multiple times. Nothing ever fixes rancher startup issues. I can never get a clean install and app startup where the cluster starts successfully and image manager is ready.

Could you open a Windows Cmd shell (not powershell) and run

set

and dump the output here (you might want to pull out any personal or sensitive info)?

hey @kind-iron-72902 - yeah i can do this. from my most recent investigations, I feel like it definitely has something to do with dns resolutions from inside rancher-desktop wsl distro, although I dont know how to fix it. Basically what i'm noticing is anything like "nslookup google.com" will always timeout inside rancher-desktop

Thanks for digging in. Would you mind opening a ticket at https://github.com/rancher-sandbox/rancher-desktop/issues ? At the least it'll make a good doc issue.

well and since hyper-v (really just hypervisor framework) is needed for WSL2 bit of a headscratcher on why things would be working if it wasn’t reinstalled

wsl2 does use some hyper-v features underneath but it doesn't actually require hyper-v be turned on explicitly as a feature in windows. Turning the actual feature on must do something else in terms of networking that breaks rancher dns resolution

yup hyper-v got split into hypervisor framework and the management side. still the same hypervisor and virtual switching under the covers.