Im not looking for a workaround actually, Im just reporting the issue in the newest version of Docker Desktop.

You can use docker inspect to get your containers IP address.

Host machine is linux that runs on Hyper-V, called MobyLinuxVM.

This can be currently done by adding appropriate routes to routing table via 10.0.75.2 (this IP of docker linux host running on HyperV I believe).

How one can reach (ping) 172.x.

Why the method with routing tabled stopped to worked, and how it can be fixed.

The problem with accessing containers by IP from windows machine.

Suppose it is default bridge network, so: docker network inspect bridge (usually something like 172.17.0.2 ).

The idea of system modifications with Windows Docker networking for that purpose made me uncomfortable.

For my situation, I found a little trick to avoid this entirely, and maybe it turns out to be useful for someone else too.

My concrete scenario was Chrome Co-Debugging with VS Code Remote Containers.

I rolled back to 19.x and it works again with the persistent route workaround.

The new Docker for Windows has built-in support for WSL2 for those who are using Windows 10 Home.

WSL2 allows you to ping the 172.0.0.1 automatically without doing route IP or whatever.

WSL2 is integrated into Windows so why not use the localhost for everything.

Docker Can'T Connect Update The Hosts

If youre a web dev u can always update the hosts automatically with some bash script.

I just build project that works for all different types of OS using HyperV, wsl2, macOS, and Linux because I use the localhost for everything.

Are you able to do that with your environment Mine looks just like yours, and Im not able to.

See this answer for your to use the docker internal DNS and you can just use service names directly.

There is a challenge where you would need to ping or connect to the container ip 172.X, which is why people are asking for help.

Docker For Mac Can'T Connect