Add support for publishing ranges of ports

[md5]

Given the ability to --expose ranges of ports from #8167, it would be useful to be able to publish ranges of ports as well. I'd like to be able to do this:

docker run -d --publish 10000-20000:10000-20000 myimage

[kfei]

👍

[cv711]

Can we please merge this one? It's quite useful. Thanks!

[krasi-georgiev]

docker run -help doesn't show the new option for port range

-p, --publish=[] Publish a container's port to the host
format: ip:hostPort:containerPort | ip::containerPort | hostPort:containerPort | containerPort
(use 'docker port' to see the actual mapping)

[krasi-georgiev]

one more bug
http://screencast.com/t/h3KuExeJr8Nj

on every port it ads new line so docker ps becomes unreadable.

[thaJeztah]

@vipconsult I think the output of ps is being worked on here; #10339

[ColmHally]

@vipconsult @thaJeztah yeah, I'll be adding published ranges in ps output later tonight on #10339

[dkirrane]

Are there any limits on port ranges?
I'm publishing approx. 200 ports
docker run -p 7000-7200 -p 8080 webservice

If I exec into the container I can curl to the webservice URL:
curl http://localhost:8080/my/web/service

But if I do same from the host ip it just gets stuck loading the page:
curl http://HOST_IP:8080/my/web/service

[thaJeztah]

@dkirrane is your webservice perhaps only listening on localhost? It should be listening on "any" IP-address (ie, 0.0.0.0)

[md5]

@dkirrane your service's ports are being published on random host ports.

Try this:

docker run -p 7000-7200:7000-7200 -p 8080:8080 webservice

[md5]

Be aware that starting a container with a large published range of ports like that is currently quite slow. I didn't dig into it, but I'm assuming the reason is that Docker is creating individual iptables rules for each port in the range instead of taking advantage of iptables's native ability to map port ranges.

[thaJeztah]

service's ports are being published on random host ports

^^ oh, correct, wasn't paying attention

[dkirrane]

@md5 Ya sorry that was a typo. I've reduced the number of ports & mapped the port-range as described:
docker run -d -p 7000-7003:7000-7003 -p 7053-7063:7053-7063 -p 8099:8099 -p 9080:9080 -p 9443:9443 --name="my-service" dkirrane/my-service

Now from the host machine if I curl to my docker service using localhost the page returns. However, when I use the Host IP curl fails

alias hostip="ip route show 0.0.0.0/0 | grep -Eo 'via \S+' | awk '{ print \$2 }'"

# Localhost works
curl http://localhost:9080/my/web/service

# Host IP returns connection timesout
curl http://$(hostip):9080/my/web/service

[md5]

I'm not sure why you're using that method to get your host IP address, but I think you're getting the wrong IP to pick up the port mapping. That command is giving you your outbound gateway address for the default route, not the host IP.