Rancher Desktop behind a proxy

[heathdbrown]

Issue rancher Desktop fails behind a proxy

Get errors in the console when launching Rancher Desktop.

The log files for docker, k8s, wsl have errors. docker and k8s looks to be attempting to reach a Public address but not utilizing a proxy.

References

• Github Issues on Rancher Deskop 995
• Github Issues on Rancher Deskrop 1267
• Microk8s configuration for proxy

[heathdbrown]

Attempted to perform and edit in the following:

• /etc/rc.conf following Rancher doesn't work on VPN / Corporate Proxy rancher-sandbox/rancher-desktop#995

• Did not work and had to remove and add back Rancher Desktop

2022-02-10T20:57:51.503Z: Running command wsl --distribution rancher-desktop --exec cp /mnt/c/Users/$USERNAME/AppData/Local/Temp/rd-k3s-pvHFQZ/k3s /etc/conf.d/k3s...
2022-02-10T20:57:52.159Z: Running command wsl --distribution rancher-desktop --exec chmod 644 /etc/conf.d/k3s...
2022-02-10T20:57:52.791Z: Running command wsl --distribution rancher-desktop --exec /sbin/rc-update --update...
2022-02-10T20:57:53.390Z: Running command wsl --distribution rancher-desktop --exec /usr/local/bin/wsl-service k3s start...
2022-02-10T20:57:54.111Z: Running command wsl --distribution rancher-desktop --exec cat /proc/net/route...
2022-02-10T20:57:54.856Z: Running command wsl --distribution rancher-desktop --exec cat /proc/net/fib_trie...
2022-02-10T20:57:56.668Z: Running command wsl --distribution rancher-desktop --exec wslpath -a -u C:\Users\$USERNAME\AppData\Local\Programs\Rancher Desktop\resources\resources\linux\wsl-helper...
2022-02-10T20:57:57.594Z: Running command wsl --distribution rancher-desktop --exec /mnt/c/Users/$USERNAME/AppData/Local/Programs/Rancher Desktop/resources/resources/linux/wsl-helper k3s kubeconfig...
/bin/wsl-service k3s stop: Error: wsl.exe exited with code 1

[heathdbrown]

error after re-installaing Rancher Desktop and modified /etc/rc.conf

Error: C:\Users\$USERNAME\AppData\Local\Programs\Rancher Desktop\resources\resources\win32\bin\kubectl.exe exited with code 255

Log states the last command ran was the following:

wsl --distribution rancher-desktop --exec /mnt/c/Users/$USERNAME/AppData/Local/Programs/Rancher Desktop/resources/resources/linux/wsl-helper k3s kubeconfig

When I run this manually I don't have an issue it just 'runs' with no output.

When I run this manually inside of rancher-desktop WSL it generates a kubernetes configuration.

[heathdbrown]

Just noticed I misspelled /etc/environment when setting the vars. That still has an issue.

[heathdbrown]

Found the following rancher-sandbox/rancher-desktop#1538

Attempted with the clearing of the unregistering and cache data, still same issue.

 wslconfig /u rancher-desktop-data
wslconfig /u rancher-desktop

cd /mnt/c/Users/$USER/AppData
rm -fr {Local,Roaming}/rancher-desktop/*

Then attempted changing the port...still the same issue, but noticed I need to do the /etc/environment and /etc/rc.conf changes again.

Still busted

[markus-obstmayer]

Is there any update regarding this issue. I have the same issue running Rancher Desktop ( Windows 10) behind a proxy.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

[tehautanop]

@heathdbrown Hi, inside WSL you might need to have proxy ip and port in /etc/environment, proxy ip and hostname in /etc/hosts, obviously do something to /etc/resolv.conf and maybe import some of you company certififcates

[heathdbrown]

Is there any update regarding this issue. I have the same issue running Rancher Desktop ( Windows 10) behind a proxy.

I don't have an update on this but it looks like I am not alone in Rancher and corporate proxy issues.

[heathdbrown]

@tehautanop we updated the /etc/environment. I am not 100% sure what the /etc/hosts or /etc/resolv.conf is going to do as everything looks to resolve correctly.