To precise my setting Windows 10 Version 20H2 Build 1904 213 rancher-users #rancher-desktop

Title

ambitious-dusk-59039

11/17/2022, 7:02 PM

To precise my setting: Windows 10, Version 20H2 (Build 1904.2130), WSL 2, Kernel version 5.10.102.1, Rancher Desktop v 1.6.2

wide-mechanic-33041

11/17/2022, 7:18 PM

this will help a bit https://docs.rancherdesktop.io/how-to-guides/running-air-gapped

it will help you get passed startup, but getting the proxy and especially an authd proxy into the VM context is not really done yet. you can hack some stuff in, but its a bit fragile and dependent on your host platform from my experience

ambitious-dusk-59039

11/21/2022, 8:02 AM

Hi Justin,

thanks for your Advises. This helps me bootstrapping a little further. Not sure if I will suceed 100% though, still trying.

wide-mechanic-33041

11/21/2022, 12:24 PM

on the proxy side https://github.com/rancher-sandbox/rancher-desktop/labels/area%2Fproxy has a lot of workarounds

miniature-advantage-69986

11/21/2022, 4:38 PM

@ambitious-dusk-59039 have you set any PROXY Environment variables. You could try this in a cmd window:

setx HTTP_PROXY <http://user:password@your_proxy_server:3128>
setx HTTPS_PROXY <https://user:password@your_ssl_proxy_server:3128>

rem see: <https://github.com/MicrosoftDocs/WSL/issues/244>
rem the separator of variables to share is ":"
setx WSLENV HTTP_PROXY:HTTPS_PROXY

After setting these variables you will have to restart Rancher-Desktop, after that you can check if the variables have been propagated by WSL by entering the following command in windows:

wsl -d rancher-desktop echo ${HTTP_PROXY}
wsl -d rancher-desktop echo ${HTTPS_PROXY}

wide-mechanic-33041

11/21/2022, 4:39 PM

one issue you might hit though been a while since I tested. https://github.com/rancher-sandbox/rancher-desktop/issues/2147

2 Views

#rancher-desktop Join Slack