-
Notifications
You must be signed in to change notification settings - Fork 18.7k
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
Reserve Docker port on IANA #1440
Comments
Pull requests accepted! |
What would we change the port to? Do you think this would turn into a never ending battle if we had to change the ports for specific setups? On Aug 7, 2013, at 5:57 AM, Nick Stinemates notifications@github.com wrote:
|
We could pick a free port and register it with IANA: https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml |
I had this issue, as well. I turned off CrashPlan and everything was fine. |
+1 about picking up a free port and registering with IANA. On Wed, Aug 7, 2013 at 7:05 AM, John Weis notifications@github.com wrote:
|
+1 I think this is something we will want to do in 1.0 On Aug 7, 2013, at 7:55 AM, Jérôme Petazzoni notifications@github.com wrote:
|
+1 The IANA Port application form is here: http://www.iana.org/form/ports-services and it would likely make most people's lives earlier to settle on the final port earlier, rather than later. I'd be happy to help out with this. To work around the issue for the moment, I did modify one line in my Vagrantfile for the moment just so the vagrant box would come up and was basically working. |
My favorites on that list of unassigned are: 100 On Wednesday, August 7, 2013 at 8:34 AM, Sean P. Kane wrote:
|
ping @shykes |
We will want to keep the port between 1024 and 49151. Things below 1025 are reserved for official protocols, and ports above 49150 are dynamic and never assigned. |
Indeed, as we didn't exclude the non-root usage of docker, it would be better to have port > 1024. I like the 2375-2380 range. |
+1 on >1024. What's the process for registering an IANA port? On Wed, Aug 7, 2013 at 4:15 PM, Guillaume J. Charmes <
|
@shykes Read the linked RFCs then fill out this form: https://www.iana.org/form/ports-services |
@shykes any news on this ? |
Is this relevant anymore now that we listen on a Unix socket by default? |
It would be nice to reserve a port for those times when TCP is used. How about 42042? 😉 |
I updated the title and description so that this can be completed. |
@shykes I'm guessing this is something we need to do soon.... |
+1. — On Wed, Nov 27, 2013 at 1:57 PM, Michael Crosby notifications@github.com
|
ping @shykes |
If someone wants to volunteer and do this, let me know. Otherwise we will schedule for sometime before 1.0. |
On 24 Jan 2014, at 15:57, Solomon Hykes wrote:
I can do it.
李柯睿 |
I can fill this out. A couple of things:
|
Ah - I should have updated - I'll setup an email address etc. |
Sorry - I meant I'll do a contact address rather than the application @liljenstolpe - sorry for the confusion. Give me ten ticks to find the right address. |
Okay - if you could use support@docker.io - that'd be awesome. |
Ok. I'll file this weekend. Two questions I'm not sure I have the immediate answers to:
|
|
(btw, I like your choice :)) |
Continuing to see CrashPlan port conflicts .... |
@robparrott Well we haven't changed the port number so that's to be expected. |
this thread started Aug 2013. many thanks to @liljenstolpe to getting the ball rolling. to be production-ready, you must have IANA ports. looks like this has been approved, as linked above, so looking forward to a port change in the near future. |
@jamtur01 @SvenDowideit there is no default value in the code anymore (since a few month), so nothing to change on that side. Could you make a PR to update the docs please ? |
@crosbymichael @vieux @unclejack can we add this to the 1.0 milestone? |
good point @vieux. We might need to change settings in boot2docker also. |
@shykes yep, This is more of a docs and b2d issue. There is nothing to change in the docker codebase because our default is a unix socket. |
ping @SvenDowideit Can you update b2d setup to use the new port? |
I'll look at the docs. |
awesome! |
@jamtur01 any update on this ? Thanks. |
Little busy. :) Will get to it this afternoon. |
2375/2376 are assigned: http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=docker For moby#1440 Docker-DCO-1.1-Signed-off-by: SvenDowideit <SvenDowideit@home.org.au> (github: SvenDowideit)
@SvenDowideit Is there anything left to do for this issue? |
Should be closed in favor of #6181. |
yes, I have a stack more b2d stuff to deal with :) but Docker is golden :) |
On 2 Jun 2014, at 18:46, ives wrote:
Welcome
李柯睿 |
The current docker port conflicts with the Crashplan software. Please reserve a port on IANA for docker.
The text was updated successfully, but these errors were encountered: