Merge pull request #6181 from SvenDowideit/change-out-port-number

IANA allocated Docker port: 2375

docs/sources/articles/basics.md

@@ -61,7 +61,7 @@ image cache.
 With `-H` it is possible to make the Docker daemon to listen on a
 specific IP and port. By default, it will listen on
 `unix:///var/run/docker.sock` to allow only local connections by the
-*root* user. You *could* set it to `0.0.0.0:4243` or a specific host IP
+*root* user. You *could* set it to `0.0.0.0:2375` or a specific host IP
 to give access to everybody, but that is **not recommended** because
 then it is trivial for someone to gain root access to the host where the
 daemon is running.
@@ -74,8 +74,8 @@ Similarly, the Docker client can use `-H` to connect to a custom port.
 
 For example:
 
--   `tcp://host:4243` -> TCP connection on
-    host:4243
+-   `tcp://host:2375` -> TCP connection on
+    host:2375
 -   `unix://path/to/socket` -> Unix socket located
     at `path/to/socket`
 
@@ -98,11 +98,11 @@ You can use multiple `-H`, for example, if you want to listen on both
 TCP and a Unix socket
 
     # Run docker in daemon mode
-    $ sudo <path to>/docker -H tcp://127.0.0.1:4243 -H unix:///var/run/docker.sock -d &
+    $ sudo <path to>/docker -H tcp://127.0.0.1:2375 -H unix:///var/run/docker.sock -d &
     # Download an ubuntu image, use default Unix socket
     $ sudo docker pull ubuntu
     # OR use the TCP port
-    $ sudo docker -H tcp://127.0.0.1:4243 pull ubuntu
+    $ sudo docker -H tcp://127.0.0.1:2375 pull ubuntu
 
 ## Starting a long-running worker process
 

docs/sources/articles/https.md

@@ -67,13 +67,13 @@ Now you can make the Docker daemon only accept connections from clients
 providing a certificate trusted by our CA:
 
     $ sudo docker -d --tlsverify --tlscacert=ca.pem --tlscert=server-cert.pem --tlskey=server-key.pem \
-      -H=0.0.0.0:4243
+      -H=0.0.0.0:2375
 
 To be able to connect to Docker and validate its certificate, you now
 need to provide your client keys, certificates and trusted CA:
 
     $ docker --tlsverify --tlscacert=ca.pem --tlscert=client-cert.pem --tlskey=client-key.pem \
-      -H=dns-name-of-docker-host:4243
+      -H=dns-name-of-docker-host:2375
 
 > **Warning**: 
 > As shown in the example above, you don't have to run the

docs/sources/installation/mac.md

@@ -33,7 +33,7 @@ virtual machine and run the Docker daemon.
 ```
 	boot2docker init
 	boot2docker start
-	export DOCKER_HOST=tcp://localhost:4243
+	export DOCKER_HOST=tcp://localhost:2375
 ```
 
 `boot2docker init` will ask you to enter an ssh key passphrase - the simplest

docs/sources/installation/ubuntulinux.md

@@ -259,9 +259,9 @@ Then reload UFW:
 
 UFW's default set of rules denies all incoming traffic. If you want to
 be able to reach your containers from another host then you should allow
-incoming connections on the Docker port (default 4243):
+incoming connections on the Docker port (default 2375):
 
-    $ sudo ufw allow 4243/tcp
+    $ sudo ufw allow 2375/tcp
 
 ## Docker and local DNS server warnings
 

docs/sources/reference/api/docker_remote_api_v1.0.md

@@ -7,7 +7,7 @@ page_keywords: API, Docker, rcli, REST, documentation
 # 1. Brief introduction
 
 -   The Remote API is replacing rcli
--   Default port in the docker daemon is 4243
+-   Default port in the docker daemon is 2375
 -   The API tends to be REST, but for some complex commands, like attach
     or pull, the HTTP connection is hijacked to transport stdout stdin
     and stderr

docs/sources/reference/api/docker_remote_api_v1.1.md

@@ -7,7 +7,7 @@ page_keywords: API, Docker, rcli, REST, documentation
 # 1. Brief introduction
 
 -   The Remote API is replacing rcli
--   Default port in the docker daemon is 4243
+-   Default port in the docker daemon is 2375
 -   The API tends to be REST, but for some complex commands, like attach
     or pull, the HTTP connection is hijacked to transport stdout stdin
     and stderr

docs/sources/reference/api/docker_remote_api_v1.10.md

@@ -1297,4 +1297,4 @@ stdout and stderr on the same socket. This might change in the future.
 To enable cross origin requests to the remote api add the flag
 "–api-enable-cors" when running docker in daemon mode.
 
-    $ docker -d -H="192.168.1.9:4243" --api-enable-cors
+    $ docker -d -H="192.168.1.9:2375" --api-enable-cors

docs/sources/reference/api/docker_remote_api_v1.11.md

@@ -1358,4 +1358,4 @@ stdout and stderr on the same socket. This might change in the future.
 To enable cross origin requests to the remote api add the flag
 "–api-enable-cors" when running docker in daemon mode.
 
-    $ docker -d -H="192.168.1.9:4243" --api-enable-cors
+    $ docker -d -H="192.168.1.9:2375" --api-enable-cors

docs/sources/reference/api/docker_remote_api_v1.12.md

@@ -1370,4 +1370,4 @@ stdout and stderr on the same socket. This might change in the future.
 To enable cross origin requests to the remote api add the flag
 "–api-enable-cors" when running docker in daemon mode.
 
-    $ docker -d -H="192.168.1.9:4243" --api-enable-cors
+    $ docker -d -H="192.168.1.9:2375" --api-enable-cors

docs/sources/reference/api/docker_remote_api_v1.2.md

@@ -7,7 +7,7 @@ page_keywords: API, Docker, rcli, REST, documentation
 # 1. Brief introduction
 
 - The Remote API is replacing rcli
-- Default port in the docker daemon is 4243
+- Default port in the docker daemon is 2375
 - The API tends to be REST, but for some complex commands, like attach
   or pull, the HTTP connection is hijacked to transport stdout stdin
   and stderr
@@ -999,5 +999,5 @@ stdout and stderr on the same socket. This might change in the future.
 To enable cross origin requests to the remote api add the flag
 "–api-enable-cors" when running docker in daemon mode.
 
-> docker -d -H="[tcp://192.168.1.9:4243](tcp://192.168.1.9:4243)"
+> docker -d -H="[tcp://192.168.1.9:2375](tcp://192.168.1.9:2375)"
 > –api-enable-cors

docs/sources/reference/api/docker_remote_api_v1.3.md

@@ -7,7 +7,7 @@ page_keywords: API, Docker, rcli, REST, documentation
 # 1. Brief introduction
 
 - The Remote API is replacing rcli
-- Default port in the docker daemon is 4243
+- Default port in the docker daemon is 2375
 - The API tends to be REST, but for some complex commands, like attach
   or pull, the HTTP connection is hijacked to transport stdout stdin
   and stderr
@@ -1081,4 +1081,4 @@ stdout and stderr on the same socket. This might change in the future.
 To enable cross origin requests to the remote api add the flag
 "–api-enable-cors" when running docker in daemon mode.
 
-> docker -d -H="192.168.1.9:4243" –api-enable-cors
+> docker -d -H="192.168.1.9:2375" –api-enable-cors

docs/sources/reference/api/docker_remote_api_v1.4.md

@@ -7,7 +7,7 @@ page_keywords: API, Docker, rcli, REST, documentation
 # 1. Brief introduction
 
 - The Remote API is replacing rcli
-- Default port in the docker daemon is 4243
+- Default port in the docker daemon is 2375
 - The API tends to be REST, but for some complex commands, like attach
   or pull, the HTTP connection is hijacked to transport stdout stdin
   and stderr
@@ -1127,4 +1127,4 @@ stdout and stderr on the same socket. This might change in the future.
 To enable cross origin requests to the remote api add the flag
 "–api-enable-cors" when running docker in daemon mode.
 
-    $ docker -d -H="192.168.1.9:4243" --api-enable-cors
+    $ docker -d -H="192.168.1.9:2375" --api-enable-cors

docs/sources/reference/api/docker_remote_api_v1.5.md

@@ -7,7 +7,7 @@ page_keywords: API, Docker, rcli, REST, documentation
 # 1. Brief introduction
 
 - The Remote API is replacing rcli
-- Default port in the docker daemon is 4243
+- Default port in the docker daemon is 2375
 - The API tends to be REST, but for some complex commands, like attach
   or pull, the HTTP connection is hijacked to transport stdout stdin
   and stderr
@@ -1134,4 +1134,4 @@ stdout and stderr on the same socket. This might change in the future.
 To enable cross origin requests to the remote api add the flag
 "–api-enable-cors" when running docker in daemon mode.
 
-    $ docker -d -H="192.168.1.9:4243" --api-enable-cors
+    $ docker -d -H="192.168.1.9:2375" --api-enable-cors

docs/sources/reference/api/docker_remote_api_v1.6.md

@@ -1235,4 +1235,4 @@ stdout and stderr on the same socket. This might change in the future.
 To enable cross origin requests to the remote api add the flag
 "–api-enable-cors" when running docker in daemon mode.
 
-    $ docker -d -H="192.168.1.9:4243" --api-enable-cors
+    $ docker -d -H="192.168.1.9:2375" --api-enable-cors

docs/sources/reference/api/docker_remote_api_v1.7.md

@@ -1229,4 +1229,4 @@ stdout and stderr on the same socket. This might change in the future.
 To enable cross origin requests to the remote api add the flag
 "–api-enable-cors" when running docker in daemon mode.
 
-    $ docker -d -H="192.168.1.9:4243" --api-enable-cors
+    $ docker -d -H="192.168.1.9:2375" --api-enable-cors

docs/sources/reference/api/docker_remote_api_v1.8.md

@@ -1275,4 +1275,4 @@ stdout and stderr on the same socket. This might change in the future.
 To enable cross origin requests to the remote api add the flag
 "–api-enable-cors" when running docker in daemon mode.
 
-    $ docker -d -H="192.168.1.9:4243" --api-enable-cors
+    $ docker -d -H="192.168.1.9:2375" --api-enable-cors

docs/sources/reference/api/docker_remote_api_v1.9.md

@@ -1312,4 +1312,4 @@ stdout and stderr on the same socket. This might change in the future.
 To enable cross origin requests to the remote api add the flag
 "–api-enable-cors" when running docker in daemon mode.
 
-    $ docker -d -H="192.168.1.9:4243" --api-enable-cors
+    $ docker -d -H="192.168.1.9:2375" --api-enable-cors

docs/sources/reference/commandline/cli.md

@@ -103,9 +103,9 @@ To use lxc as the execution driver, use `docker -d -e lxc`.
 The docker client will also honor the `DOCKER_HOST` environment variable to set
 the `-H` flag for the client.
 
-    $ docker -H tcp://0.0.0.0:4243 ps
+    $ docker -H tcp://0.0.0.0:2375 ps
     # or
-    $ export DOCKER_HOST="tcp://0.0.0.0:4243"
+    $ export DOCKER_HOST="tcp://0.0.0.0:2375"
     $ docker ps
     # both are equal