Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with docker.for.mac.host.internal #1448

Closed
GinoPane opened this issue Mar 23, 2018 · 6 comments
Closed

Issue with docker.for.mac.host.internal #1448

GinoPane opened this issue Mar 23, 2018 · 6 comments
Labels

Comments

@GinoPane
Copy link
Contributor

GinoPane commented Mar 23, 2018

Info:

  • Docker version ($ docker --version): 17.12.0-ce, build c97c6d6
  • Laradock commit ($ git rev-parse HEAD): 0077de2
  • System info (Mac, PC, Linux): MacOS Sierra
  • System info disto/version: 10.12 (16A323)

Issue:

Host IP may change that's why I wanted to utilize newly Mac-only DNS name docker.for.mac.host.internal. I set it tinto my .env file and got this error when I tried to start containers afterwards:

ERROR: for laradock_workspace_1 Cannot create container for service workspace: invalid IP address in add-host: "docker.for.mac.host.internal"


Expected behavior:

Docker Host IP should be populated correctly

@spyridonas
Copy link
Contributor

After a bit of searching I found a use who said
"Nevermind, I forgot that a program I'm running called Freedom messes up networking for some Docker images." Can you try that?

@GinoPane
Copy link
Contributor Author

@spyridonas No, it's not the case for me :)

@bestlong
Copy link
Member

@GinoPane why docker.for.mac.host.internal need manual setting?
just use it in container.

@GinoPane
Copy link
Contributor Author

@bestlong This is the issue actually, I wanted to use it and set it in .env file (as DOCKER_HOST variable), which further populates docker-compose.yaml and got this error when building containers.

@stale
Copy link

stale bot commented Feb 2, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Stale label Feb 2, 2020
@stale
Copy link

stale bot commented Feb 23, 2020

Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period. We really really appreciate your contributions, and looking forward for more in the future 🎈.

@stale stale bot closed this as completed Feb 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants