Docker Container No route to host error

[henscu (Henry Scullion)]

I have a similar problem when running wp-super-cache plugin on WordPress using Docker for Mac. The cURL calls from wp-super-cache from inside my WordPress container to http://localhost:8081 (I am mapping ports using -p 8081:80) are failing.

There are many other posts on this problem on this forum. This is the one I got most info from:

Access host (not vm) from inside container

Expected behavior Be able to access an ipv4 or ipv6 address, or some DNS/hostname from inside a container which can access the host (not the xhyve/hyper-v vm). There’s a few issues posted on this forum that are similar, but all the solutions are hacks and most revolve around using hostnet networking, where it’s apparent that Docker wants to focus on supporting nat networking (as it has recently become the default). An example use case is an application running inside a container which must con…

And this is the official documentation on workarounds for the issue as far as I can see. In my case, as the call is being made from a third party plugin, I may have to hack it to update the address the cURL command uses. I will see if I can make it work.

Explore networking features on Docker Desktop