I’m trying to understand the behavior of the docker.for.mac.localhost pseudo-dns entry in Docker for Mac as part of deploying OpenWhisk with a local CouchDB instance on my Mac. (Caveat – yes, I could try to run CouchDB in the docker-verse, but that really isn’t a good long-term plan.) So, here’s t…

Understanding the 'docker.for.mac.localhost' behavior

jamshid (Jamshid) May 7, 2018, 5:21am 5

Okay docker.for.mac.host.internal is deprecated, they switched to host.docker.internal.

DNS name host.docker.internal should be used for host resolution from containers. Older aliases (still valid) are deprecated in favor of this one. (See draft-west-let-localhost-be-localhost-06).

2 Likes

Topic		Replies	Views
Docker.local not resolving on host (mac) and vm's Docker Desktop dns , docker , beta	2	3043	June 4, 2016
.localhost DNS doesn't resolve in browsers other than Chrome Docker Desktop macos	3	9298	August 29, 2017
Docker for mac does not add docker hostname to /etc/hosts Docker Desktop	8	19777	May 4, 2016
Fail to resolve docker.local Docker Desktop dns	3	2091	May 12, 2016
Any idea why docker.for.mac.localhost would work in one container but not another? Docker Desktop macos	0	4578	July 7, 2017

Understanding the 'docker.for.mac.localhost' behavior

Related topics