cli Windows WSL2 connection issue

I am behind a corporate firewall and the windows firewall is also managed. When I try to use devcontainer cli from WSL I am unable to reach the DNS. Is there a way to track down why and where the traffic may be blocked between WSL and Host Windows in order to be able to use devcontainer CLI ?

Jan 15 '24 08:01 hinogi

Looping in @chrmarti for insights ^

Jan 19 '24 00:01 samruddhikhandale

Do you get a reply when running nslookup ghcr.io in WSL? (I get 140.82.121.33.)

Jan 22 '24 13:01 chrmarti

first, there is no nslookup in the wsl :D I just tried wget for the same effect and it doesn't work.

Jan 22 '24 20:01 hinogi

What is wget's output? Which Linux distro are you using?

Jan 23 '24 09:01 chrmarti

wget cannot resolve the name, i tried wslvpnkit that seems to solve a bit of it. I use the default Ubuntu 20.04. but additionally, the devcontainer has no internet when I am able to start it :D

Jan 23 '24 13:01 hinogi

Could this be an issue with WSL's network setup? What do you get for wsl --version and have you tried wsl --update?

Jan 24 '24 08:01 chrmarti

There is no wsl --version and wsl --update requires elevated rights

Jan 25 '24 06:01 hinogi

Could this be https://stackoverflow.com/questions/62314789/no-internet-connection-on-wsl-ubuntu-windows-subsystem-for-linux?

Jan 25 '24 08:01 chrmarti

Could this be https://stackoverflow.com/questions/62314789/no-internet-connection-on-wsl-ubuntu-windows-subsystem-for-linux?

Actually my problem seems more specific in that regard because, I am able to ping ip addresses but not domain names.

Jan 25 '24 13:01 hinogi