Question

Docker --net=host does not forward ports

On my local machine setting --net=host on a container makes the container visible on any ports it is using. On a Docker Ubuntu 16.04 droplet the port is not accessible with --net=host.

Simplified Example:

This works: docker run -p 8000:8000 -it python python -m http.server

This does not work: docker run --net=host -p 8000:8000 -it python python -m http.server

How can I make the ports of the container application exposed with docker run --net=host ...?

Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Sorry to see that your question hasn’t received an answer yet. I’ve just spun up a new Docker Droplet (17.12.0~ce on 16.04) and was able to access port 8000 using both commands you posted, as well as just docker run --net=host -it python python -m http.server. I had to open port 8000 on the firewall, though (ufw allow 8000).

It’s possible that it was a temporary issue that was resolved.