Docker Community Forums

Share and learn in the Docker community.

Access container from the host network

(Prathert) #1

Expected behaviour

–net=host should enable other users in the host network to access the container.
Before switching to docker for MAC we used virtual box and could configure the system in a way that other users could have access to the container.

Actual behavior

I learned that net=host is not working at the moment, but I was wondering if there is any other option to assign a static host network address to the container to allow other users to access the container. a workaround would be really great and I didn’t find this so far in the forum or docker documentation.

unfortunately I am a total beginner to all this and would need a step by step and very detailed explanation…


Docker for Mac: version: mac-v1.12.0-beta17
OS X: version 10.11.3 (build: 15D21)
logs: /tmp/20160630-115152.tar.gz
[OK] docker-cli
[OK] app
[OK] menubar
[OK] virtualization
[OK] system
[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

(David Maze) #2

As a general rule, no. On Linux you could probably set up a complicated bridge-network setup where your containers could talk directly to the physical network, but that’s complicated and definitely not the usual Docker setup. I have no idea how I’d start to do anything like this on Mac.

Does the normal docker run -p option to expose container ports on the host work? If not, why not? (You should rarely need --net host in normal operation.)

(Prathert) #3

Sorry I did not give enough details.

I am running proftp inside the container and would like to allow users to access it via passive mode.
This was possible before with net=host.

I cannot change the proftp settings without messing around with a lot of other stuff. Therefore, any idea how to solve this on the container end would be great…

(Prathert) #4

no idea? anybody?
still trying to figure that out…