Anyone get the following error when running

docker pull hello-world

on a corporate machine using a vpn with MITM inspection and proxy for most endpoints.

Error response from daemon: Get "<https://registry-1.docker.io/v2/>": dial tcp <http://142.xxx.xxx.xxx:443|142.xxx.xxx.xxx:443>: connect: connection refused

you need to configure the proxy server. now WSL has moproxy and the new autoproxy native feature so guessing you are on macos or linux? Also assume you are using a PAC which makes it more complicated to pull the proxy URL automatically. I have used override.yaml to set my envs as Jan mentions in this Issue so that may be a good option. I don't think there is a better pattern for corp internet proxies delivered via PAC for the moment, but def could be wrong there.

Thanks I'll check this out. I'm on windows 11 using wsl. Are you saying with wsl if I set autoProxy=true it allows network communication in wsl? currently I use wsl-vpnkit.

vpnkit solves a different problem. thats where your vpn breaks the virtual switching on your machine. there are other settings in RD to help get traffic out of your machine. autoproxy should set the http_proxy vars in the machine as part of its init process helping to avoid needing to set manually. you can use

rdctl shell

to see what is going on in the container host