Expected behavior docker run --net=host ... should connect to local ports/services Actual behavior It doesn’t. Information OS X: version 10.11.5 (build: 15F34) Docker.app: version v1.11.1-beta13.1 Running diagnostic tests: [OK] Moby booted [OK] driver.amd64-linux [OK] vmnetd …

xhyve is still not an actual real native in-OSX implementation. It’s virtualization software. It is just the native virtualization software (thus no need to bundle vbox). But docker is still running a linux virtual machine in the background. Getting an actual real native container requires writing…

Yes, I understand that docker running in xhyve is not native-- it’s similar to Docker Toolbox with a VirtualBox image running docker natively. So, for a third time… the question still remains… Should docker run –net=host work or not?

To explain again: docker run --net=host should work. It does work. It attaches to the ports on the host machine which is the virtual machine inside xhyve. If you expect it to connect to your Mac’s host ports, then no. It will not do that, because it’s running on a virtual machine. “… it’s similar …

[image] snowgirl: To explain again: docker run --net=host should work. It does work. It attaches to the ports on the host machine which is the virtual machine inside xhyve. […] Why would one ever think changing virtualization engines would change that? Because the overall direction of the M…

Yes, a -p works so well, because it’s opening a localport that is actually a redirect to an address that is NATed behind the docker bridged networking. It is not docker running on the Linux machine that is instigating this port opening. The invoking agent on the Mac knows exactly which port needs t…

I would expect that because I’ve been “sold” docker for mac not “docker under a different virtualization engine.” FitNesse tests that run under docker on mac in a virtual box work, but do not work “natively” because FitNesse can not connect to the exposed web interfaces running in the docker contain…

-p doesn’t work like it does in Linux. For example: %>docker run -p 8765:8765 ua-cloud %>curl localhost:8765/start Cloud OK %>docker run -p 8765:8765 --net=host ua-cloud %>curl localhost:8765/start curl: (7) Failed to connect to localhost port 8765: Connection refused Under linux, I can get d…

[image] Docker for Mac and Windows Beta: the simplest way to use Docker on your laptop -... Since June 20th, 2016, Docker for Mac and Windows are now publicly available. You can download them at docker.com/products/overview To celebrate Docker’s third birthday, today we start a limited a…

Well, I guess since this issue isn’t going to be accepted as an issue or fixed, then Docker for make is a non-starter for me. I assumed “Docker for mac” meant my Docker images that work out of the box in Linux would work in Mac. They don’t and when I report they don’t, I’m told “that’s not the goal…

Should docker run --net=host work?

Docker Desktop

mcgeeco (Conor McGee) June 7, 2016, 4:49pm 11

Also being discussed here (since April). Is it really that hard for someone to just clarify the current situation around this (is it a known issue?) and what the plans are?

Topic		Replies	Views
Explain networking known limitations, explain "host" Docker Desktop macos	12	14692	July 20, 2023
Confused about networking defaults, how to get VM IP with native port forwarding off? Docker Desktop	15	6425	September 28, 2016
Access host (not vm) from inside container Docker Desktop beta , macos	40	127171	June 18, 2018
Beta 9 and localhost connection via net=host Docker Desktop macos	15	10627	June 15, 2016
--net=host does not work Docker Desktop	8	26422	July 10, 2016

Should docker run --net=host work?

Related topics