You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have tried with the latest version of my channel (Stable or Edge)
I have uploaded Diagnostics
Expected behavior
Hosts file contains the correct IP address for the primary network interface for both host.docker.internal and gateway.docker.internal.
Actual behavior
Docker for Windows pulls the IP address of a random network adapter (usually one that's not even connected), and uses that as the IP address.
Information
Windows Version: 10.0.19042.546
Docker Desktop Version: 2.4.0.0
Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: No
Steps to reproduce the behavior
Have multiple network cards connected to a machine, and randomly connect/disconnect them to get the wrong IP address populated.
Proposed solution
Allow the user to specify which network adapter to use for populating the host.docker.internal and gateway.docker.internal addresses. At the very minimum, give us the option to turn the auto-update of the IP address off. Or, even better, define a loopback network interface with a known IP address so you don't have to mess with the hosts file constantly!
The text was updated successfully, but these errors were encountered:
Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.
Prevent issues from auto-closing with an /lifecycle frozen comment.
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.
/lifecycle stale
Expected behavior
Hosts file contains the correct IP address for the primary network interface for both
host.docker.internal
andgateway.docker.internal
.Actual behavior
Docker for Windows pulls the IP address of a random network adapter (usually one that's not even connected), and uses that as the IP address.
Information
Steps to reproduce the behavior
Have multiple network cards connected to a machine, and randomly connect/disconnect them to get the wrong IP address populated.
Proposed solution
Allow the user to specify which network adapter to use for populating the
host.docker.internal
andgateway.docker.internal
addresses. At the very minimum, give us the option to turn the auto-update of the IP address off. Or, even better, define a loopback network interface with a known IP address so you don't have to mess with the hosts file constantly!The text was updated successfully, but these errors were encountered: