Support tap interface for direct container access (incl. multi-host)

almirkadric · July 19, 2017, 3:00pm

Time to make some waves, this issue has been going on for too long and enough is enough

github.com/docker/docs

Statement that inability to route to containers due to OSX limitation is inaccurate

opened 02:53PM - 19 Jul 17 UTC

closed 05:09PM - 14 Oct 17 UTC

AlmirKadric

lifecycle/locked

The statements under the points `I cannot ping my containers` and `Per-container… IP addressing is not possible` are inaccurate. These are not limitations of macOS nor limitations of hyperkit. This is purely a limitation of Docker for Mac. To prove this very point I have created the following package which allows users to work around the issue by installing a shim to overwrite the arguments used to start hyperkit: https://github.com/AlmirKadric-Published/docker-tuntap-osx If Docker for Mac has no plans to fix the OSX routing issue natively by either allowing the networking options for the hyperkit instance to be configured, or having a tap interface by default (similar to hvint0 on Windows), the documentation should reflect that users can use the above project to workaround the issue. If for any reason the above project is insufficient in your opinion, please let me know and I will fix them. If you believe that such a project should not be required, there is already a group of people behind that statement (myself included) and we would love to see this issue fixed at the source `Docker for Mac` For more details, see original issue: https://forums.docker.com/t/support-tap-interface-for-direct-container-access-incl-multi-host/17835/21 File: [docker-for-mac/networking.md](https://docs.docker.com/docker-for-mac/networking/), CC @londoncalling

github.com/docker/for-mac

Docker for Mac and docker network access from host

opened 12:02PM - 08 Aug 16 UTC

closed 03:20PM - 18 Nov 16 UTC

stefanfoulis

kind/enhancement area/network version/1.12.0 osx/10.11.x status/acknowledged lifecycle/locked

### Expected behavior I can access all containers by ip address from my OSX hos…t directly. ### Actual behavior I can't access containers by network unless I map ports to 127.0.0.1. ### Information Diagnostic ID: 13B73004-5CA7-40F3-B597-AA61D1FC6C37 Docker for Mac: 1.12.0 (Build 10871) macOS: Version 10.11.6 (Build 15G31) [OK] docker-cli [OK] app [OK] moby-syslog [OK] disk [OK] virtualization [OK] system [OK] menubar [OK] osxfs [OK] db [OK] slirp [OK] moby-console [OK] logs [OK] vmnetd [OK] env [OK] moby [OK] driver.amd64-linux ### Steps to reproduce the behavior 1. `docker run --name=httpd -d httpd` 2. `docker inspect httpd` extract IPAddress from the output (e.g `172.17.0.2`) 3. `curl http://172.17.0.2/` - expected to get the apache page, but get a timeout ### Notes I understand that the reason for this not working, is that this is due to the documented fact that there is no `docker0` interface available on osx (https://docs.docker.com/docker-for-mac/networking/#/there-is-no-docker0-bridge-on-osx). For our workflow (allowing the host to access containers directly from the host, without port mapping) it is pretty crucial. So my main question is, if there are plans to support this or if it is an impossible to overcome technical hurdle.

github.com/docker/for-mac

Access the Containers from Host like on Linux

opened 03:03PM - 06 Aug 16 UTC

KartoffelToby

kind/feature area/network status/acknowledged lifecycle/frozen

# This is a kind of a requst Hello there, i have a testing development scenari…o build with docker containers. on linux machines i can access them via the conatinaer IP (172.17.0.X) and intacting via the exposed Port. But on Docker for Mac this isn't possible because i dont know the IP from the VM with the Toolbox (Docker Machine) i can route 172.17.0.x to docker machine ip.. is there any way to do that with Docker for Mac? I need this because i have multiple Database Containers each with the same Port... (so -p istn't the answer ;))

Topic		Replies	Views
Network bridge on host Docker Desktop beta , macos	6	23912	October 17, 2023
Explain networking known limitations, explain "host" Docker Desktop macos	12	14544	July 20, 2023
Customizing subnet of bridge network Docker Desktop	4	5614	June 27, 2016
OSX connection sharing confuses Docker for Mac Docker Desktop	1	1326	June 2, 2016
Cannot access network port on host using bridge network Docker Desktop	1	13955	August 5, 2016

Support tap interface for direct container access (incl. multi-host)

Related topics