![docker desktop windows 8.1 docker desktop windows 8.1](https://i.stack.imgur.com/BCgEW.png)
Wireless LAN adapter Local Area Connection* 10:Įthernet adapter Bluetooth Network Connection: Wireless LAN adapter Local Area Connection* 7: : 192.168.0.1Įthernet adapter VirtualBox Host-Only Network: (I've modified Ethernet 3's IP address since it's in the corporate network) ip -br a One hint - something that doesn't make sense to me - is this from inside a container: /]# ping 172.26.183.209
![docker desktop windows 8.1 docker desktop windows 8.1](https://i.ytimg.com/vi/F3bccaS9iMM/maxresdefault.jpg)
![docker desktop windows 8.1 docker desktop windows 8.1](https://blogs.sap.com/wp-content/uploads/2019/02/enable-k8s.png)
Nmap done: 1 IP address (0 hosts up) scanned in 0.43 /]# curl Ĭurl: (7) Failed to connect to 172.26.183.209 port 8080: No route to host Nmap done: 1 IP address (1 host up) scanned in 0.02 curl > /dev/null So now that I have a web server listening on port 8080 in a process my WSL2, it can be accessed with, as confirmed by nmap and curl from WSL2: nmap -Pn -p 8080 172.26.183.209 I also have a corporate Forticlient VPN that could be messing this up.
DOCKER DESKTOP WINDOWS 8.1 HOW TO
I'm pretty sure that when I reboot in a moment, all will be fine and dandy.ĭo you have an idea on how to debug something this? I'm getting used to rebooting when I run into WSL2+DockerDesktop problems, but now I'd like to finally understand what is actually wrong. But today that doesn't work for some reason. Normally, I can access a port started from a WSL2 instance ("distribution" in WSL2-speak) from inside Docker containers, by finding the IP address of the WSL2 instance, and referencing to that IP address from inside the containers. It seems I'm constantly running into networking problems when using WSL2 and Docker Desktop for Windows.