Publish to random host port while using –network=host

I am trying to access a host URL from within a docker container. I would also like to publish container ports to random ports on the host.

docker run --network=host -P -d somerepo/someimage

However, it looks like the -P and the --net=host options don’t want to co-exist as I don’t see any port mappings created when I run a docker ports <container_id>

  • error retrieving template Job(deis-router@.service) from Registry in ec2 deis installation
  • Installing docker on azure virtual machine windows 10
  • Environment variables for docker-compose inside of Jenkins
  • Submit docker which contains fat jar to Spark cluster
  • swarm, kubernetes or mesos for batch processing jobs
  • Spring MVC - String Parameter with '-' resolved as '?'
  • Am I missing something obvious here?

    PS: There is no docker-machine involved. Docker engine is running directly on the host machine.

  • Docker Ubuntu 12.04
  • Yesod Persona authentication problems when using Dockerized MongoDB
  • docker-compose: console does not return to host when creating database container
  • Where to hold Application Files - Docker
  • docker container vs swarm communication issue
  • Vagrant + docker errors
  • One Solution collect form web for “Publish to random host port while using –network=host”

    You can’t use -P or -p with --net=host because that doesn’t make any sense. When you’re using --net=host, IF a process in a container opens a port THEN that port is open on your host. No mapping is required, because your container process are running in the host’s network environment.

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