mirror of https://github.com/docker/cli.git
Update documentation for EXPOSE
The documentation for EXPOSE seems to indicate, that EXPOSE is only relevant in the context of links, which is not the case. Signed-off-by: Jacob Atzen <jatzen@gmail.com>
This commit is contained in:
parent
407a4a1916
commit
d40014d096
|
@ -329,10 +329,13 @@ default specified in `CMD`.
|
||||||
The `EXPOSE` instructions informs Docker that the container will listen on the
|
The `EXPOSE` instructions informs Docker that the container will listen on the
|
||||||
specified network ports at runtime. Docker uses this information to interconnect
|
specified network ports at runtime. Docker uses this information to interconnect
|
||||||
containers using links (see the [Docker User
|
containers using links (see the [Docker User
|
||||||
Guide](/userguide/dockerlinks)). Note that `EXPOSE` only works for
|
Guide](/userguide/dockerlinks)) and to determine which ports to expose to the
|
||||||
inter-container links. It doesn't make ports accessible from the host. To
|
host when [using the -P flag](/reference/run/#expose-incoming-ports).
|
||||||
expose ports to the host, at runtime,
|
**Note:**
|
||||||
[use the `-p` flag](/userguide/dockerlinks).
|
`EXPOSE` doesn't define which ports can be exposed to the host or make ports
|
||||||
|
accessible from the host by default. To expose ports to the host, at runtime,
|
||||||
|
[use the `-p` flag](/userguide/dockerlinks) or
|
||||||
|
[the -P flag](/reference/run/#expose-incoming-ports).
|
||||||
|
|
||||||
## ENV
|
## ENV
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue