-
Notifications
You must be signed in to change notification settings - Fork 119
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
NetworkSettings are incorrect/unusable when binding on specific IPs #4541
Comments
When running Docker Desktop, the actual daemon (and containers) are running in a lightweight VM; I think in this case there's some "magic" in Docker Desktop that captures your That said, if your intent is to make the port accessible on your machine's IP-address, you can omit the IP-address ( |
Yes I do understand the mechanics here, but we have tools relying on the data in network settings and those are breaking now. This all used to work very well in 2.1.0.5, the last version before assigning to specific IPs started failing (see #4209 ). So i downgraded. I can see the 'intended" mapping in Looks like a regression to me |
This comment reports magic happening at client side, might be part of the issue |
I think these changes are in the proxy that's used to map the docker socket inside the VM to the host. When bind-mounting the docker socket in a container ( |
@thaJeztah do you happen to have any information about where the code for that proxy is? Looks like it may be some private repo? I wonder if I can access the proxy from within docker (instead of using the docker socket) |
That proxy is part of the proprietary code in Docker Desktop, so cant link to the code itself. If you connect to the docker socket on your host machine (mac/win) that docker is proxied. (disclaimer: I'm not on the Docker Desktop team, so don't have answers to all the nitty-gritty details 😅🤗) |
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. |
/remove-lifecycle stale |
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. |
/remove-lifecycle stale |
/lifecycle frozen |
Update: The problem is still there, and the Reproducing, using my local IP (10.0.0.106):
Mapping works very well.
Docker inspect has no more label i could use to find the mapping, and nothing mentions "8080" in there
Even the new Docker dashboard has no idea what's happening. If there was something to link back what I docker run it would be very helpful. Thank you! |
Just found out the labels are available in the /containers call of the docker api... but not the /containers/
|
Hi, we have a preview build that should fix this issue here: https://desktop.docker.com/mac/preview/60183/Docker.dmg. |
Thanks for your work on that! |
I confirm this preview build solves this issue 🎉 🎉 🎉 🎉 ! Do you know which version this will make it in? |
@lindycoder in the next version 😁 |
Thank you very much! |
Have the test cluster listen on a real ip instead of localhost so that porter can run on it and connect to the cluster. This relies on a preview build of docker for mac which should be released shortly. docker/for-mac#4541 (comment) Signed-off-by: Carolyn Van Slyck <[email protected]>
I think that this upgrade broke our stack:
|
This is fixed in versions 3.2.0 and 3.2.1. Closing the ticket now. |
@stephen-turner actually, it was introduced by v3.2.0 and fixed in v3.2.2 |
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. |
When I try to bind on a specific IP, the network settings shows a host/port that are unusable
I really need to be able to rely on the
NetworkSettings
Expected behavior
See the actual published IP and Port in
docker ps
and theNetworkSettings.Ports
Actual behavior
I see
localhost:32XXX
which i cannot connect toInformation
192.168.0.45
is my IP Address.After starting this container, connecting to
192.168.0.45:8080
DOES work, why does mydocker ps
shows127.0.0.1:32775
which doesn't work ?Full output of docker inspect
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: