kotovalexarian-likes-github/moby--moby
1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
Code Releases Activity

Doc update to clarify random port mapping on docker run -P

Browse source 
Signed-off-by: Dan Cotora <d@bluevision.ro>
This commit is contained in:
Dan Cotora 2014-09-22 08:36:20 +03:00
parent 39ed048aab
commit a8775d2f9a
2 changed files with 6 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
docs/man/docker-run.1.md
View file

@ -186,8 +186,9 @@ and foreground Docker containers.
When set to true publish all exposed ports to the host interfaces. The
default is false. If the operator uses -P (or -p) then Docker will make the
exposed port accessible on the host and the ports will be available to any
client that can reach the host. To find the map between the host ports and the
exposed ports, use **docker port**.
client that can reach the host. When using -P, Docker will bind the exposed
ports to a random port on the host between 49153 and 65535. To find the
mapping between the host ports and the exposed ports, use **docker port**.
**-p**, **--publish**=[]
Publish a container's port to the host (format: ip:hostPort:containerPort |

5
docs/sources/reference/run.md
View file

@ -381,8 +381,9 @@ with `-P` or `-p,` or start the client container with `--link`.
If the operator uses `-P` or `-p` then Docker will make the exposed port
accessible on the host and the ports will be available to any client
that can reach the host. To find the map between the host ports and the
exposed ports, use `docker port`)
that can reach the host. When using `-P`, Docker will bind the exposed
ports to a random port on the host between 49153 and 65535. To find the
mapping between the host ports and the exposed ports, use `docker port`.
If the operator uses `--link` when starting the new client container,
then the client container can access the exposed port via a private