-
Notifications
You must be signed in to change notification settings - Fork 18.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow specifying a range of ports to EXPOSE #1834
Comments
+1, it would be super useful. We'd also need the same thing with |
Currently as of 09-12-2013 this work should be completed in this branch: Note that there is a new |
Awesome, thanks so much for both the project and your time! :) |
I have an initial implementation (https://github.com/jhorey/docker/) under branch 1834-portrange. You can use this feature via the CLI by typing "docker -expose 8001-8101/tcp ...". Updated documentation is still missing and you can't do this via docker file yet. I'm new to the dev. community here, and I'm not quite sure what the protocol is (when to submit a pull request, etc.). |
@jhorey are you still working on this ? |
@vieux I haven't done anything more since the pull request. I do hope to add more features (Dockerfile, and maybe the ability to publish port ranges) in the near future. I'd like to get feedback though to see what people prefer. |
+1 this looks awesome |
+1 looking forward to the release |
+1 it is needed ... for example for asterisk to work .. i need a range of UDP ports to be forwarded |
@jhorey It looks like you opened a PR against your own master branch. In order to get this into Docker, I think you need to open a PR against dotcloud/master. You can probably do that by closing your current PR, opening a new one, then before sending it click 'Edit' next to 'master...1834-portrange' and change the base. |
+1. How can I help get this pushed? |
+1 this would be very useful as I need to expose 21100 to 21199 for Couchbase clusters |
I plan on rebasing my branch and submitting a new PR early this week. I do have an implementation question though: when "linking" a client to a server, does that actually change anything on the client wrt to iptables, or does it just modify the environment variables? |
I've updated my PR, but I'm not sure how to attach it to this thread. Here's the new issue: #4795 |
How do I remove a port range or other entries in the boot2docker-vm.vbox file? I edit this file when the vm is shutdown, then start and after shutdown again all the ports are back |
Using --expose at container runtime worked for me - better, actually, as it doesn't require adding yet another intermediate container at image build time. |
@maxx I meant how do I remove the ip range once its already in the vm file. I was able to figure it out. |
Any updates on this? Just discovered that I need it for Freeswitch--or, rather, I need it if I don't want an EXPOSE for every RTP port. :) |
+1 for hadoop ephemeral AM ports |
+1 |
Can't wait to use this... My container (Cloud9 IDE) spawns different services at random ports each time we do a "Run" from the UI... Thanks! |
👍 |
+1 +1 +1 ! |
I need it for Freeswitch RTP ports... |
I worked around with --net=host .. which binds to any ports on the host. Works well. |
Yes, with --net=host works fine. |
--net=host works in certain applications. However, it limits you to running one of the same kind of container (unless further config is done to change the ports that the listening daemons use.) |
fwiw, +1 : databases, asterisk , freeswitch etc etc all need this. I want to be able to run several asterisk containers , but finding it very difficult to contend with the RTP ports |
My
|
Closed by #8167 |
+1 : This is wonderful news! Any word on when this feature will be released to the world? -- Hugh |
NetworkDB testing infra
It would be handy to be able to
EXPOSE
a range of ports for some applications which require a specific large-ish (100+) range of ports to be open within the container.The text was updated successfully, but these errors were encountered: