Skip to content
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

Closed
wants to merge 6 commits into from
Closed

1834 expose range #4795

wants to merge 6 commits into from

Conversation

jhorey
Copy link

@jhorey jhorey commented Mar 20, 2014

Attempt 2 for issue #1834

@SvenDowideit
Copy link
Contributor

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:
Docker-DCO-1.1-Signed-off-by: Joe Smith <joe.smith@email.com> (github: github_handle)

Please rebase and sign each commit.

@SvenDowideit
Copy link
Contributor

@jhorey can you please update the relevant documentation too?

@jhorey
Copy link
Author

jhorey commented Mar 21, 2014

@SvenDowideit sure thing, I'll update & sign and get back to you.

@creack
Copy link
Contributor

creack commented Apr 1, 2014

@jhorey Any news on this?

@dhm116
Copy link

dhm116 commented Apr 10, 2014

👍

@vieux
Copy link
Contributor

vieux commented Apr 18, 2014

@jhorey Any news on this?

@jhorey
Copy link
Author

jhorey commented Apr 18, 2014

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:

@jhorey https://github.com/jhorey Any news on this?


Reply to this email directly or view it on GitHubhttps://github.com//pull/4795#issuecomment-40847992
.

--James

@crosbymichael
Copy link
Contributor

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!

@j0hnsmith
Copy link

I'd love to see this merged.

@jstoja
Copy link
Contributor

jstoja commented Jun 30, 2014

@jhorey up?

@m1no
Copy link

m1no commented Jul 9, 2014

@jhorey would be great to have that feature :) thanks for your work already

@cxreg
Copy link

cxreg commented Aug 12, 2014

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.

@bruce
Copy link

bruce commented Aug 17, 2014

Also needed here; hoping someone with more time can volunteer!

@hesco
Copy link

hesco commented Sep 6, 2014

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.

@archetypalsxe
Copy link

I would also enjoy having this available. Guess I'll be writing a bash script to manually take care of this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet