-
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
1834 expose range #4795
1834 expose range #4795
Conversation
Can you please sign their commits following these rules: https://github.com/dotcloud/docker/blob/master/CONTRIBUTING.md#sign-your-work Each commit in your PR must be signed in the following format: Please rebase and sign each commit. |
@jhorey can you please update the relevant documentation too? |
@SvenDowideit sure thing, I'll update & sign and get back to you. |
@jhorey Any news on this? |
👍 |
@jhorey Any news on this? |
Yes, I've been meaning to push this out. Estimating in the next week or so. On Friday, April 18, 2014, Victor Vieux notifications@github.com wrote:
--James |
I'm closing this for bookkeeping, please feel free to reopen or ping us to reopen when you have time to work on this. Thanks! |
I'd love to see this merged. |
@jhorey up? |
@jhorey would be great to have that feature :) thanks for your work already |
I need this done as well. If the author is unable to re-push this work under the posted guidelines, maybe someone else should take over. I'm willing to volunteer if this is acceptable. |
Also needed here; hoping someone with more time can volunteer! |
On #docker irc channel, cpuguy83 responded to my question about this saying: "PR's are welcome, but I'd say it's relatively low priority for everyone;" to which I replied: The discussion on that issue listed plenty of folks needing to build telephony servers (asterisk, freeswitch) like I am now doing, as well as folks mentioning several other applications which need this range-of-ports feature. I'm afraid that go is a learning curve not high on my list at the moment. Though I certainly appreciate what you folks have done with it. I'm still coming up to speed on the docker command set myself though. Shame the core team does not consider this a higher priority as it would make docker more relevant and easier to administer for a large number of applications which need to expose port ranges. |
I would also enjoy having this available. Guess I'll be writing a bash script to manually take care of this |
Attempt 2 for issue #1834