host.docker.internal does not resolve properly

[128keaton]

• I have uploaded Diagnostics
• I have tried with the latest version of my channel (Stable or Edge)
• Diagnostics ID: 80B22EC8-EBD9-42FA-ABC5-67F685FD5DD1

Expected behavior

host.docker.internal to resolve properly

Actual behavior

host.docker.internal does not resolve to anything.

Information

• macOS Version: 10.12.6

Diagnostic logs

Docker for Mac: version: 18.03.1-ce-mac65 (dd2831d4b7421cf559a0881cc7a5fdebeb8c2b98)
macOS: version 10.12.6 (build: 16G1314)
logs: /tmp/80B22EC8-EBD9-42FA-ABC5-67F685FD5DD1/20180601-094343.tar.gz
[OK]     vpnkit
[OK]     vmnetd
[OK]     dns
[OK]     driver.amd64-linux
[OK]     virtualization VT-X
[OK]     app
[OK]     moby
[OK]     system
[OK]     moby-syslog
[OK]     kubernetes
[OK]     files
[OK]     env
[OK]     virtualization kern.hv_support
[OK]     osxfs
[OK]     moby-console
[OK]     logs
[OK]     docker-cli
[OK]     disk

Steps to reproduce the behavior

(simple demo)

1. docker run --rm alpine nslookup host.docker.internal
2. 

(use in dev)

services:
  php:
    build:
      context: dev/docker/php
      args:
        TIMEZONE: ${TIMEZONE}
        LOCAL_USER_ID: ${LOCAL_USER_ID}
    networks:
      main:
        aliases:
          - php
    environment:
      COMPOSER_ALLOW_SUPERUSER: 1
    volumes:
      - nfsmount:/var/www/site
      - ~/.ssh:/home/www-data/.ssh
volumes:
  nfsmount:
    driver: local
    driver_opts:
      type: nfs
      o: addr=addr=host.docker.internal,rw,nolock,hard,nointr,nfsvers=3
      device: ":${PWD}"

Running docker-compose up with this configuration results in:
ERROR: for php Cannot create container for service php: error resolving passed in nfs address: lookup addr=host.docker.internal: no such host

I have tried rebooting and resetting Docker. I'd rather not update to 10.13.

[deedree]

I've got the same problem on Mac OS Mojave 10.14. docker system prune --volumes as mentioned here: #2705 didn't work either.

[PeterBengtson]

I have exactly the same problem. It makes networking between services impossible to set up on the Mac. I add my vote for a quick fix, as this is a showstopper in many Mac dev projects.

[128keaton]

@PeterBengtson I had to move back to using Vagrant while the rest of the team happy enjoys Docker because of this issue.

[allyjweir]

Has there been any progress on this issue?

[findstar]

I have exactly the same problem. on Mac OS Mojave.

[anaerobic]

Same problem on OSX Mojave (10.14) using Version 18.06.1-ce-mac73 (26764)

However, docker.for.mac.host.internal does resolve to the correct IP.

[FernandoMiguel]

I'm using this with latest stable Docker and docker-compose with NFS on the latest macos and it works fine..
I'll retest today to be sure.

[ror6ax]

Hi @PeterBengtson @128keaton, can you please let us know what is the status here? Thanks a lot.

[PeterBengtson]

Situation resolved - it was a question of using the right IP for resolving in the nginx proxy conf. tis 6 nov. 2018 kl. 11:10 skrev Gregory Reshetniak <notifications@github.com

…

: Hi @PeterBengtson <https://github.com/PeterBengtson> @128keaton <https://github.com/128keaton>, can you please let us know what is the status here? Thanks a lot. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2965 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAPObSEz54HEAe6cWVxnWqXPpuUel1qks5usWAHgaJpZM4UXAjw> .

[ror6ax]

Not sure how nginx factors in here. I have checked and can confirm host.docker.internal is not being resolved on my 18.06 which prevents me from using docker

…

On Tue, 6 Nov 2018, 13:09 Peter Bengtson ***@***.*** wrote: Situation resolved - it was a question of using the right IP for resolving in the nginx proxy conf. tis 6 nov. 2018 kl. 11:10 skrev Gregory Reshetniak < ***@***.*** >: > Hi @PeterBengtson <https://github.com/PeterBengtson> @128keaton > <https://github.com/128keaton>, can you please let us know what is the > status here? Thanks a lot. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#2965 (comment)>, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/AAAPObSEz54HEAe6cWVxnWqXPpuUel1qks5usWAHgaJpZM4UXAjw > > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2965 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACRlBanMhEa-3ytEvzRJ3HdTl-Twme_sks5usXvmgaJpZM4UXAjw> .

[qoomon]

have a look at https://github.com/qoomon/docker-host as a workaround

[carusology]

I also had this issue. Reinstalling with the latest stable version (18.06.1-ce-mac73) caused the host.docker.internal DNS entry to resolve to the host machine in my containers. I am also running macOS 10.14 (Mojave).

My original installation was pretty old (I'd applied updates, but never reinstalled anew) that had some dns haxin' lingering as described in this issue. Maybe it was related?

[deedree]

Reinstall fixed it for me. Thanks!