-
Notifications
You must be signed in to change notification settings - Fork 289
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
Windows container cannot resolve host.docker.internal, but Linux container can. #10504
Comments
I'm having similar problems. Inside my container:
The image I am using is: mcr.microsoft.com/dotnet/framework/aspnet:4.7.2-windowsservercore-ltsc2019 Docker Desktop on Win10 - DockerEngine v20.10.2 |
Running into this issue as well:
|
This issue was been tracking here: #1976 |
Issues go stale after 90 days of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
My windows docker container cannot resolve host.docker.internal, but it's working with Linux containers.
I am on version 20.10.2. Could this be bug 1976 reported for version 18?
My application gives this runtime error:
System.Net.Sockets.SocketException: No such host is known
I've tried pinging host.docker.internal.
FROM mcr.microsoft.com/dotnet/framework/runtime:4.8-windowsservercore-ltsc2019
ARG source
WORKDIR /app
COPY ${source:-SampleApp/obj/Docker/publish} .
ENTRYPOINT ["C:\app\SampleApp.exe"]
The text was updated successfully, but these errors were encountered: