https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
w
probably just the proxy as there is minimal clean proxy support in the product today. Lots of “it depends” and timing for the most part especially on Windows. Mac is a bit better because the full VM is a bit easier to manage. VPN can drive issues w MTU. DNS should be pretty solid with the hostresolver so without any specific errors its hard to know your issue. Have you jumped into the shell (
rdctl shell
) to see what is working and what isn’t?
p
it seems that the rancher-desktop image is not able to connect to web
either a DNS problem or a firewall
but there is no chances to have network working
also tryed to change the nameserver to 8.8.8.8 with no success
the screenshot is from the colleacue that has the problem and is at home with wifi+vpn and no docker run or docker pull
w
looks like it found a DNS name for docker.io and it looks like proxy is your issue.
p
we also tryed to deactivate firewall defender just in case with no success
no since we also tryed to curl by IP
w
did you try to curl something on your intranet?
p
in linux there is no proxy info and also in the windows env no proxy
w
so you don’t have a proxy on the other side of the VPN?
you have a direct route to the internet from your corp network to the internet basically
p
I still have to undestand out network since it seems to be a mess 🤔 but when we have to use VPN we do not need proxy
we tryed both by IP and also on an interna IP with no avail
how can I chack if the windows firewall is in the way?
w
look at the firewall logs
p
we disabled but I'm not sure since this behaviour is too strange and all seems to point to it
can you point me to where logs are placed?
could it also be the antivirus?
we have mcafee trillix
w
p
thanks
w
and if your VPN has broken routing for the WSL2 instance it could be the cause. if you cant ping an intranet resource from your the rancher shell, but can from your windows CMD than i would think your vpn has broken the WSL2 routing
p
could be BUT how can we fix it?
w
work with your vpn supplier
some say use of hyper-v virtual switching is not supported on vpn clients
p
ummm but only with those 2 PC?
w
no clue on your counts or configs just trying to point at places to look
p
because the strange thing is that these 2 colleagues are the only 2 unlucky ones that have this problem
all the others do not have this problem (and all PC should be fairly similar)
we'll try to build up a matrix of all versions and pieces
will send you all updates
w
thats good news as you have a known good. so you just need to diff the machines. see what works and move step by step forward. start at basic network checks from the distro to more complicated interactions
p
got a couple of news, installing on the same PC so under same conditions a ubuntu distribution it manages to exit using curl (things that it did not manage to do before
so the problem could be in the resolv.conf and wsl.conf of the rancher desktop distro?
w
well resolv.conf should just point to the host resolver process which forwards queries to whatever dns is configured on the host
p
but is the host_resolver process something that comes with rancher desktop or is from windows? since it seems that ubuntu is getting the info properly and rancher desktop no
This is the ipconfig from the windows system
in the ubuntu we have this
this is the ip addr show of ubuntu
and this works
now we tryed to do a factory reset and we get this
Copy code
Error: connect ECONNREFUSED 192.168.1.2:6443

2022-10-07T10:20:32.123Z: Registered distributions: 
2022-10-07T10:20:37.540Z: Registered distributions: rancher-desktop
2022-10-07T10:20:37.825Z: Registered distributions: rancher-desktop
2022-10-07T10:20:37.826Z: Creating initial data distribution...
2022-10-07T10:20:56.764Z: Unmounting missing device /dev/sdc: 120 119 8:32 / /mnt/wsl/rancher-desktop/run/data rw,relatime shared:2 - ext4 /dev/sdc rw,discard,errors=remount-ro,data=ordered
2022-10-07T10:20:57.202Z: Did not find a valid mount, mounting /mnt/wsl/rancher-desktop/run/data
2022-10-07T10:21:04.201Z: WSL: executing: cat /root/.docker/config.json: Error: wsl.exe exited with code 1
2022-10-07T10:21:14.333Z: Installing C:\Users\2152\AppData\Local\Programs\Rancher Desktop\resources\resources\linux\internal\trivy as /mnt/c/Users/2152/AppData/Local/Programs/Rancher Desktop/resources/resources/linux/internal/trivy into /usr/local/bin/trivy ...
2022-10-07T10:21:14.433Z: Installing C:\Users\2152\AppData\Local\Programs\Rancher Desktop\resources\resources\linux\internal\rancher-desktop-guestagent as /mnt/c/Users/2152/AppData/Local/Programs/Rancher Desktop/resources/resources/linux/internal/rancher-desktop-guestagent into /usr/local/bin//rancher-desktop-guestagent ...
w
so lots of things going on here. did you test networking, ping an ip, ping a name, curl an internal site, curl an external site?
p
yes we did: the host is working correctly as espected and also the Ubuntu distribution installed on WSL as a second distribution to test it ... so wsl and windows are working correctly is the rancher desktop distro or something else that is not connecting to the network at all; now we will try to uninstall it and reinstall it to see what happens, do you have any hint of what could have gone wrong?
w
nope not enough data to make a call on what might be the issue
p
here is some results:
1. Download wsl-vpnkit.tar.gz and copy in C:\Users\<username> 2. Open PowerShell in C:\Users\<username> and execute wsl.exe --import wsl-vpnkit $env:USERPROFILE\wsl-vpnkit wsl-vpnkit.tar.gz wsl.exe -d wsl-vpnkit wsl.exe -d wsl-vpnkit service wsl-vpnkit start 3. Open WSL rancher-desktop wsl -d rancher-desktop Go to root /mnt/d/tmp/extractor # cd /root edit ~ # vi .profile add and save wsl.exe -d wsl-vpnkit service wsl-vpnkit status >/dev/null || \ wsl.exe -d wsl-vpnkit service wsl-vpnkit start 4. restart Rancher Desktop 5. Open PowerShell check WSL wsl-vpnkit e rancher-desktop are running with this:
wsl -l -v
NAME STATE VERSION wsl-vpnkit Running 2 rancher-desktop-data Stopped 2 rancher-desktop Running 2 Open WSL rancher-desktop wsl -d rancher-desktop check ping # ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: seq=0 ttl=64 time=2.328 ms
please see if this helps you understanding if there is something that has to be added to RD. This solved the problem for us
17 Views
Open in Slack
PreviousNext
Powered by