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>

  • Boot2Docker to Google Compute Engine VM: saving Docker container
  • Docker in docker connection error
  • Running multiple docker instances in EC2
  • Explanation of this docker file?
  • How can I create a stream for DockerDotNet BuildImageFromDockerfile method?
  • setting up cadvisor through API
  • Am I missing something obvious here?

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

  • Docker-Compose Issue with container name
  • Creating a docker image from an existing enviornment
  • Private Docker Registry with Azure Storage and Nginx: 502 Bad Gateway
  • AWS ECS container logs design pattern
  • How to modify the `--registry-mirror` of a running docker machine?
  • Installation of chef-client(Bootstrapping) on docker container in a VM on Azure/AWS
  • 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.