DockerMan and port range improvements

[Capt.Insano]

Now that Docker supports exposing and forwarding whole port ranges since v 1.6 any chance of updating DockerMan to support same?:

 

What I was thinking was the ability to do this:

 

 

to eliminate this:

 

 

from what I have read here (open to correction) a docker container can alse be run with

 

run -d --name="CONTAINERNAME" --net="bridge"  -p 59960-59970:59960-59970/tcp  -v "VOLUME":"VOLUME":rw 

 

Would love some opinions.

 

Thanks,

 

The Capt.

[Capt.Insano]

I have been experimenting with it just to ensure it works: I can run a deluge container for example from the command line with:

 

/usr/bin/docker run -d --name="Deluge" --net="bridge" -e TZ="Europe/London" -p 48921-48930:48921-48930/tcp -p 58846:58846/tcp -p 8112:8112/tcp -v "/mnt/cache/Docker/AppData/Deluge":"/config":rw -v "/mnt/user/Downloads/Deluge":"/downloads":rw needo/deluge

 

and the port range 58921-48930 are set up correctly and the container runs.

 

The DockerMan WebUI however still lists all the ports individually like my 2nd screenshot in the OP.

 

Is this even a possible improvement to DockerMan?

 

Thanks again,

 

The Capt.

[jonp]

Going to move this to the roadmap as it's not a defect report, but a feature request.

[Capt.Insano]

Thanks for moving this, the subheading of the Defect Reports subforum reads:

 

"Post bug reports and feature enhancement suggestions here."

 

 

That is why I thought it was the correct location for it.

 

Thanks,

 

The Capt.