Expected behavior Previously (e.g. with docker machine and earlier betas) it was not possible to establish a TCP connection to a container port from the Mac host unless the both (a) the port was exposed with a port binding and (b) the container was actually listening on its internal port. Actual be…

@richnorth Thanks for the details and great steps to reproduce. I was able to replicate the issue on my end and have created ticket #4015 within our internal issue tracker. Keep an eye out for a fix within the changelogs.

Port forwarding of exposed ports behaves unexpectedly

Docker Desktop

richnorth (Richard North) June 18, 2016, 10:21pm 3

Thanks @frenchben that’s great to hear.

Thank you very much, and I’ll look out for the fix

Topic		Replies	Views
Unbound container ports accept connections when using "Expose container ports on localhost" Docker Desktop windows	3	4000	July 25, 2016
Mapped port on localhost accepts connection immediately, before container starts listening on it's port Docker Desktop	0	632	May 27, 2016
Exposed ports not available on host Docker Desktop	0	2419	June 29, 2016
Port mappings not accessible on Mac Docker Desktop beta	3	2541	July 2, 2016
Port forward not working on a macOS installation but works on others Testcontainers macos	8	26226	October 26, 2023

Port forwarding of exposed ports behaves unexpectedly

Related topics