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
Support host.docker.internal instead of dockerhost #2966
Comments
hastinbe
added a commit
to hastinbe/laradock
that referenced
this issue
May 7, 2021
Fixes laradock#2966 where current versions of laradock containers are already making DNS requests to host.docker.internal which resolving NXDOMAIN when it should resolve. See docker/for-linux#264 moby/moby#40007 https://docs.docker.com/engine/release-notes/#networking-2 for docker-engine 20.10 Signed-off-by: Beau Hastings <[email protected]>
3 tasks
Hi 👋 this issue has been automatically marked as |
Hi again 👋 we would like to inform you that this issue has been automatically |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
While troubleshooting why phpunit initialization was slow, I found there are DNS lookups for host.docker.internal that are not resolving from the workspace container.
Expected Behavior:
host.docker.internal should resolve to the docker host
Context information:
Output of
git rev-parse HEAD
Output of
docker version
Output of
docker-compose version
System info: Mac, Windows or Linux. Include which disto/version
Stacktrace & Additional info:
We should be getting a local response for
host.docker.internal
. Laradock is configured to usedockerhost
for the docker host indocker-compose.yml
. Replacingdockerhost
withhost.docker.internal
indocker-compose.yml
resolves this problem. Likewisehost.docker.internal
falls in-line with Mac and Windows, and recent support for it in docker 20.10.The text was updated successfully, but these errors were encountered: