If I had to keep the network, it is possible to change the subnet in the docker-compose file.

So when I was pinging the physical dev server, it was trying to find it on the virtual docker network, where it didn't exist.Īfter deleting that network (it was a dev one I didn't use), everything worked.

which overlapped my physical server IP address range. pattern didn't work.įinally I discovered through doing docker network inspect on the networks I had locally that one had created with the same subnet of 172.16. But the physical dev server which sat on a 172.16. IP pattern) or the random sites on the internet I was able to receive a response. I was using a bridge network on my local machine for a service I was developing and ran into similar issues, what was weird was that pinging our production physical servers (which started with a 10.10. I wanted to throw this answer out as it happened to me on Windows, but could really on any environment.