This message was deleted.
# rancher-desktop
a
This message was deleted.
j
Hmm, looks like the image build uses a proxy. And you say the problem happens when you are on the VPN. Those two things have been the source of problems in the past, and I'm not sure what the current state of RD is there. @calm-sugar-3169 does this ring a bell?
c
@white-doctor-91032 which version of rancher desktop are you using?
w
Morning! the last version 1.8.1 I don't know if the problem is related to this https://github.com/rancher-sandbox/rancher-desktop/issues/722 and the workaround is this https://github.com/sakai135/wsl-vpnkit
Finally I managed to access the VPN and the internet with Rancher Desktop by installing version v0.3.8 wsl-vpnkit, the last one does not work in Rancher, it prevents Rancher Desktop from booting. Then executing the command wsl.exe -d wsl-vpnkit --cd /app wsl-vpnkit And magically everything works perfectly. It is not a Rancher Desktop problem, it is a WLS 2 problem.
🎉 2
c
Hi Jose, you don’t need to use the WSL vpn kit, as of
1.8.1
we have introduced a solution that should work with VPN, you can enable it by
Copy code
rdctl set --experimental.virtual-machine.networking-tunnel=true
Also, you can learn more about it here: https://github.com/rancher-sandbox/rancher-desktop/issues/3810
r
Yeah I second that, we originally had a lot of issues with working behind a corporate VPN but this setting resolved it for us on 1.8.1 and we do not have to use vpnkit. I have run into that same error and found that setting the docker proxy in the VM, restarting, setting my system proxy and adding the proxy to the Dockerfile ENV fixed it all.
Also, beware until 1.9 comes out, there is a minor bug with the allowed images and that experimental function. @calm-sugar-3169 fixed it but it is coming out in 1.9