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>

  • How to use nginx with docker as a reverse proxy
  • docker service create image command like `docker run`
  • Shared memory with docker
  • cannot run container after commit changes
  • Is it possible to run a command when stopping a Docker container?
  • docker cp a folder with a relative symlink: invalid symlink
  • Am I missing something obvious here?

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

  • Vagrant + puppet + docker
  • docker push denied: Unable to determine the upload's size
  • Docker Devmapper space issue - increase size
  • How to suppress marathon accessing logs in “docker logs”?
  • Eval command not found when completing the Docker for Windows tutorial
  • Re-Installing Boot2Docker fails due to apparent VirtualBox running - how to shut them down?
  • 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.