p4u1/docker-cli
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Doc update to clarify EXPOSE vs -p functionality.

Browse Source 
Signed-off-by: Daniel Farrell <dfarrell@redhat.com>
Upstream-commit: 5730abc16728404c328b896c893f9487effbec55
Component: engine
This commit is contained in:
Daniel Farrell
2014-09-28 19:45:41 -04:00
parent ffcbd2813b
commit aa28ecc957
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
components/engine/docs/sources/reference/builder.md
View File

@ -268,7 +268,10 @@ default specified in `CMD`.
The `EXPOSE` instructions informs Docker that the container will listen on the
specified network ports at runtime. Docker uses this information to interconnect
containers using links (see the [Docker User
Guide](/userguide/dockerlinks)).
Guide](/userguide/dockerlinks)). Note that `EXPOSE` only works for
inter-container links. It doesn't make ports accessible from the host. To
expose ports to the host, at runtime,
[use the `-p` flag](/userguide/dockerlinks).
## ENV