From 1d2bb271aceb6ad0a4b1e1bf803dee6492d94093 Mon Sep 17 00:00:00 2001 From: Daniel Farrell Date: Sun, 28 Sep 2014 19:45:41 -0400 Subject: [PATCH] Doc update to clarify EXPOSE vs -p functionality. Signed-off-by: Daniel Farrell --- docs/sources/reference/builder.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/sources/reference/builder.md b/docs/sources/reference/builder.md index c1e43189c7..ea9122407d 100644 --- a/docs/sources/reference/builder.md +++ b/docs/sources/reference/builder.md @@ -273,7 +273,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