This message was deleted.

i would take a look at WSL itself.

wsl --status

or

wsl --version

and likely you will want to do a

wsl --update

to make sure you are not on an ancient version

Thanks. I'm already on the latest version

WSL version: 2.2.4.0

are you able to run another distro as it seems like WSL is toast on your machine

WSL runs fine, I've got several distros working for a long time.

rancher-desktop

is running in WSL. Is there a log file or something I can check it's internal status ?

maybe https://stackoverflow.com/questions/10461257/an-attempt-was-made-to-access-a-socket-in-a-way-forbidden-by-its-access-permissi

Thanks, I'll check that out. I should have said that my Windows username has an apostrophe in it - I wonder would that cause an escaping issue somewhere? I also noticed an issue with eth0 at the bottom of

wsl-init.log

2024-06-21T18:42:37.387Z: + NETWORK_SETUP_LOG='/mnt/c/Users/JasonO'"'"'Connell/AppData/Local/rancher-desktop/logs/network-setup.log'
+ VM_SWITCH_LOG='/mnt/c/Users/JasonO'"'"'Connell/AppData/Local/rancher-desktop/logs/vm-switch.log'
+ '[' 458 -ne 1 ]
+ exec /usr/local/bin/network-setup --logfile '/mnt/c/Users/JasonO'"'"'Connell/AppData/Local/rancher-desktop/logs/network-setup.log' --vm-switch-path /usr/local/bin/vm-switch --vm-switch-logfile '/mnt/c/Users/JasonO'"'"'Connell/AppData/Local/rancher-desktop/logs/vm-switch.log' --unshare-arg /usr/local/bin/wsl-init
2024-06-21T18:42:38.175Z: + NETWORK_SETUP_LOG='/mnt/c/Users/JasonO'"'"'Connell/AppData/Local/rancher-desktop/logs/network-setup.log'
+ VM_SWITCH_LOG='/mnt/c/Users/JasonO'"'"'Connell/AppData/Local/rancher-desktop/logs/vm-switch.log'
+ '[' 1 -ne 1 ]
+ IFS=:
+ mount --make-shared /
2024-06-21T18:42:38.176Z: + mount --make-shared /etc/rancher
2024-06-21T18:42:38.177Z: + mount --make-shared /var/lib
+ mount bpffs -t bpf /sys/fs/bpf
2024-06-21T18:42:38.197Z: + mount --make-shared /sys/fs/bpf
+ mount --make-shared /sys/fs/cgroup
2024-06-21T18:42:38.198Z: + mount -t binfmt_misc binfmt_misc /proc/sys/fs/binfmt_misc
2024-06-21T18:42:38.198Z: + mount --make-shared /proc/sys/fs/binfmt_misc
+ '[' -f /var/lib/resolv.conf ]
2024-06-21T18:42:38.198Z: + exec /sbin/init
2024-06-21T18:42:38.202Z: 
2024-06-21T18:42:38.203Z:    [1m[32mOpenRC [1m[36m0.52.1[m is starting up [1m[34mLinux 5.15.153.1-microsoft-standard-WSL2 (x86_64) [DOCKER][m
2024-06-21T18:42:38.205Z:  [1m[32m*[m /proc is already mounted[K
2024-06-21T18:42:38.208Z:  [1m[32m*[m /run/openrc: creating directory[K
 [1m[32m*[m /run/lock: correcting mode[K
 [1m[32m*[m /run/lock: correcting owner[K
2024-06-21T18:42:38.209Z:  [1m[32m*[m Caching service dependencies[K ...
2024-06-21T18:42:38.249Z: ip: can't find device 'eth0'
2024-06-21T18:42:38.273Z:  [1m[31m*[m /etc/fstab does not exist[K
2024-06-21T18:42:38.319Z: Service `hwdrivers' needs non existent service `dev'
 [ ok ]
 [1m[32m*[m Starting busybox crond[K ...
 [ ok ]
2024-06-21T18:42:38.345Z: ip: can't find device 'eth0'
2024-06-21T18:42:38.351Z:  [1m[32m*[m Getting IP address for eth0[K ...
2024-06-21T18:42:38.363Z: ip: can't find device 'eth0'
2024-06-21T18:42:38.364Z:  [1m[31m*[m Could not find IP address for eth0[K
2024-06-21T18:42:38.364Z:  [ !! ]
2024-06-21T18:42:38.364Z:  [ !! ]
2024-06-21T18:42:38.365Z:  [1m[31m*[m ERROR: host-resolver failed to start[K
2024-06-21T18:42:38.372Z:  [1m[32m*[m Starting Rancher Desktop Guest Agent[K ...
2024-06-21T18:42:38.374Z:  [ ok ]

yeah i could see some script and escaping going sideways in that case. doesn't hurt to see if it changes the experience and then open an Issue on the repo if it confirms

Thanks for the help Justin. Unfortunately, I couldn't get RD to even detect WSL when I installed as another user. I uninstalled, rebooted and re-installed - still no luck. So I'm going to pass on RD for now. I'll try revisit towards the end of the year.

I'm seeing this issue as well. Any luck?