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

Reserve Docker port on IANA #1440

Closed
spkane opened this issue Aug 7, 2013 · 69 comments
Closed

Reserve Docker port on IANA #1440

spkane opened this issue Aug 7, 2013 · 69 comments
Milestone

Comments

@spkane
Copy link
Contributor

@spkane spkane commented Aug 7, 2013

The current docker port conflicts with the Crashplan software. Please reserve a port on IANA for docker.

@keeb
Copy link
Contributor

@keeb keeb commented Aug 7, 2013

Pull requests accepted!

@crosbymichael
Copy link
Contributor

@crosbymichael crosbymichael commented Aug 7, 2013

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:

Pull requests accepted!


Reply to this email directly or view it on GitHub.

@titanous
Copy link
Contributor

@titanous titanous commented Aug 7, 2013

@weisjohn
Copy link

@weisjohn weisjohn commented Aug 7, 2013

I had this issue, as well. I turned off CrashPlan and everything was fine.

@jpetazzo
Copy link
Contributor

@jpetazzo jpetazzo commented Aug 7, 2013

+1 about picking up a free port and registering with IANA.
The whole 42XX range is taken (
https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?&page=80
)
We could pick one port in those:
https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=unassigned

On Wed, Aug 7, 2013 at 7:05 AM, John Weis notifications@github.com wrote:

I had this issue, as well. I turned off CrashPlan and everything was fine.


Reply to this email directly or view it on GitHubhttps://github.com//issues/1440#issuecomment-22253390
.

@crosbymichael
Copy link
Contributor

@crosbymichael crosbymichael commented Aug 7, 2013

+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 about picking up a free port and registering with IANA.
The whole 42XX range is taken (
https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?&page=80
)
We could pick one port in those:
https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=unassigned

On Wed, Aug 7, 2013 at 7:05 AM, John Weis notifications@github.com wrote:

I had this issue, as well. I turned off CrashPlan and everything was fine.


Reply to this email directly or view it on GitHubhttps://github.com//issues/1440#issuecomment-22253390
.


Reply to this email directly or view it on GitHub.

@spkane
Copy link
Contributor Author

@spkane spkane commented Aug 7, 2013

+1
I agree, that picking an unassigned port and registering it is the best approach, and the reason, I didn't just submit a pull request with a random change that "worked for me".

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.
config.vm.forward_port 4243, 14243

@calavera
Copy link
Contributor

@calavera calavera commented Aug 7, 2013

My favorites on that list of unassigned are:

100
787
1001

On Wednesday, August 7, 2013 at 8:34 AM, Sean P. Kane wrote:

I agree, that picking an unassigned port and registering it is the best approach, and the reason, I didn't just submit a pull request with a random change that "worked for me".
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.

config.vm.forward_port 4243, 14243


Reply to this email directly or view it on GitHub (#1440 (comment)).

@crosbymichael
Copy link
Contributor

@crosbymichael crosbymichael commented Aug 7, 2013

ping @shykes

@spkane
Copy link
Contributor Author

@spkane spkane commented Aug 7, 2013

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.

@creack
Copy link
Contributor

@creack creack commented Aug 7, 2013

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.

@shykes
Copy link
Contributor

@shykes shykes commented Aug 8, 2013

+1 on >1024. What's the process for registering an IANA port?

On Wed, Aug 7, 2013 at 4:15 PM, Guillaume J. Charmes <
notifications@github.com> wrote:

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.


Reply to this email directly or view it on GitHubhttps://github.com//issues/1440#issuecomment-22291569
.

@titanous
Copy link
Contributor

@titanous titanous commented Aug 8, 2013

@shykes Read the linked RFCs then fill out this form: https://www.iana.org/form/ports-services

@vieux
Copy link
Contributor

@vieux vieux commented Aug 15, 2013

@shykes any news on this ?

@metalivedev
Copy link
Contributor

@metalivedev metalivedev commented Aug 17, 2013

Is this relevant anymore now that we listen on a Unix socket by default?

@justone
Copy link
Contributor

@justone justone commented Aug 17, 2013

It would be nice to reserve a port for those times when TCP is used. How about 42042? 😉

@crosbymichael
Copy link
Contributor

@crosbymichael crosbymichael commented Aug 17, 2013

I updated the title and description so that this can be completed.

@crosbymichael
Copy link
Contributor

@crosbymichael crosbymichael commented Nov 27, 2013

@shykes I'm guessing this is something we need to do soon....

@shykes
Copy link
Contributor

@shykes shykes commented Nov 27, 2013

+1.


Sent from Mailbox for iPhone

On Wed, Nov 27, 2013 at 1:57 PM, Michael Crosby notifications@github.com
wrote:

@shykes I'm guessing this is something we need to do soon....

Reply to this email directly or view it on GitHub:
#1440 (comment)

@creack
Copy link
Contributor

@creack creack commented Jan 9, 2014

ping @shykes

@shykes
Copy link
Contributor

@shykes shykes commented Jan 24, 2014

If someone wants to volunteer and do this, let me know. Otherwise we will schedule for sometime before 1.0.

@liljenstolpe
Copy link

@liljenstolpe liljenstolpe commented Jan 25, 2014

On 24 Jan 2014, at 15:57, Solomon Hykes wrote:

If someone wants to volunteer and do this, let me know. Otherwise we
will schedule for sometime before 1.0.

I can do it.

Christopher

Reply to this email directly or view it on GitHub:
#1440 (comment)

李柯睿
Check my PGP key here: http://www.asgaard.org/cdl/cdl.asc
Current vCard here: http://www.asgaard.org/cdl/cdl.vcf

@liljenstolpe
Copy link

@liljenstolpe liljenstolpe commented Jan 25, 2014

I can fill this out. A couple of things:

  1. It would be good if there was an e-mail address (say iana@docker.io) so that my personal address isn't in the request. Not that I mind, but it may be nice if there is an address that is always pointing at someone who can answer questions.

  2. I am going to try to grab one of the 2375-2380 range, as it's the only suggestion here in a useful range 1024 < x > 49150.

@jamtur01
Copy link
Contributor

@jamtur01 jamtur01 commented Jan 25, 2014

Ah - I should have updated - I'll setup an email address etc.

@jamtur01
Copy link
Contributor

@jamtur01 jamtur01 commented Jan 25, 2014

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.

@jamtur01
Copy link
Contributor

@jamtur01 jamtur01 commented Jan 25, 2014

Okay - if you could use support@docker.io - that'd be awesome.

@liljenstolpe
Copy link

@liljenstolpe liljenstolpe commented Jan 25, 2014

Ok. I'll file this weekend. Two questions I'm not sure I have the immediate answers to:

  1. How are we supporting versioning in the protocol
  2. Security - are we using TLS, mandatory or negotiated?
@creack
Copy link
Contributor

@creack creack commented Jan 25, 2014

  1. We are using a HTTP REST API at the moment, the version is handled by the URL, not by the port.
  2. We do not have (yet) SSL/TLS. But it should come soon
@creack
Copy link
Contributor

@creack creack commented Jan 25, 2014

(btw, I like your choice :))

@robparrott
Copy link

@robparrott robparrott commented Jun 2, 2014

Continuing to see CrashPlan port conflicts ....

@jamtur01
Copy link
Contributor

@jamtur01 jamtur01 commented Jun 2, 2014

@robparrott Well we haven't changed the port number so that's to be expected.

@neurogenesis
Copy link

@neurogenesis neurogenesis commented Jun 3, 2014

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.

@vieux
Copy link
Contributor

@vieux vieux commented Jun 3, 2014

@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 ?

@shykes
Copy link
Contributor

@shykes shykes commented Jun 3, 2014

@crosbymichael @vieux @unclejack can we add this to the 1.0 milestone?

@shykes
Copy link
Contributor

@shykes shykes commented Jun 3, 2014

good point @vieux. We might need to change settings in boot2docker also.

@vieux vieux modified the milestones: 1.0, 1.1 Jun 3, 2014
@crosbymichael
Copy link
Contributor

@crosbymichael crosbymichael commented Jun 3, 2014

@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.

@crosbymichael
Copy link
Contributor

@crosbymichael crosbymichael commented Jun 3, 2014

ping @SvenDowideit

Can you update b2d setup to use the new port?

@jamtur01
Copy link
Contributor

@jamtur01 jamtur01 commented Jun 3, 2014

I'll look at the docs.

@SvenDowideit
Copy link
Contributor

@SvenDowideit SvenDowideit commented Jun 3, 2014

awesome!

@vieux
Copy link
Contributor

@vieux vieux commented Jun 3, 2014

@jamtur01 any update on this ? Thanks.

@jamtur01
Copy link
Contributor

@jamtur01 jamtur01 commented Jun 3, 2014

Little busy. :) Will get to it this afternoon.

SvenDowideit added a commit to SvenDowideit/docker that referenced this issue Jun 3, 2014
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
Copy link
Contributor

@SvenDowideit SvenDowideit commented Jun 3, 2014

@jamtur01 @vieux I've made the docs PR, more to come (in other PRs) I expect

SvenDowideit added a commit to SvenDowideit/boot2docker that referenced this issue Jun 3, 2014
SvenDowideit added a commit to SvenDowideit/docker that referenced this issue Jun 3, 2014
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)
@unclejack
Copy link
Contributor

@unclejack unclejack commented Jun 4, 2014

@SvenDowideit Is there anything left to do for this issue?

@jamtur01
Copy link
Contributor

@jamtur01 jamtur01 commented Jun 4, 2014

Should be closed in favor of #6181.

@jamtur01 jamtur01 closed this Jun 4, 2014
vishh added a commit to vishh/docker that referenced this issue Jun 4, 2014
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
Copy link
Contributor

@SvenDowideit SvenDowideit commented Jun 5, 2014

yes, I have a stack more b2d stuff to deal with :) but Docker is golden :)

@liljenstolpe
Copy link

@liljenstolpe liljenstolpe commented Jun 9, 2014

On 2 Jun 2014, at 18:46, ives wrote:

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.

Welcome


Reply to this email directly or view it on GitHub:
#1440 (comment)

李柯睿
Avt tace, avt loqvere meliora silentio
Check my PGP key here: http://www.asgaard.org/cdl/cdl.asc
Current vCard here: http://www.asgaard.org/cdl/cdl.vcf

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

Successfully merging a pull request may close this issue.

None yet