Docker container doesn't expose ports when –net=host is mentioned in the docker run command

I have a CentOS docker container on a CentOS docker host. When I use this command to run the docker image docker run -d --net=host -p 8777:8777 ceilometer:1.x the docker container get host’s IP but doesn’t have ports assigned to it.

If I run the same command without “–net=host” docker run -d -p 8777:8777 ceilometer:1.x docker exposes the ports but with a different IP. The docker version is 1.10.1. I want the docker container to have the same IP as the host with ports exposed. I also have mentioned in the Dockerfile the instruction EXPOSE 8777 but with no use when “–net=host” is mentioned in the docker run command.

  • Cannot create container with more than 127 parents
  • How to setup nginx and django with docker-compose?
  • Docker doesn't open ports
  • Connection issue with Docker
  • Permission issue with Baikal in docker container
  • WSO2 version 2 docker files
  • pthreads process-shared memory when using: docker run --ipc --pid
  • Error loading psycopg2 module when installed from a 'wheel'
  • How to determine the Docker image ID for a tag via Docker Hub API?
  • How can I combine ENV statement in Dockerfile?
  • Docker Machine can ssh but not scp
  • supervoord gave up nodejs entered FATAL state
  • One Solution collect form web for “Docker container doesn't expose ports when –net=host is mentioned in the docker run command”

    The docker version is 1.10.1. I want the docker container to have same ip as the host with ports exposed.

    When you use --net=host it tells the container to use the hosts networking stack. So you can’t expose ports to the host, because it is the host (as far as the network stack is concerned).

    docker inspect might not show the expose ports, but if you have an application listening on a port, it will be available as if it were running on the host.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.