From aa28ecc957ca83a2b0c7b529d6fda0d1fbe13087 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 Upstream-commit: 5730abc16728404c328b896c893f9487effbec55 Component: engine --- components/engine/docs/sources/reference/builder.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/components/engine/docs/sources/reference/builder.md b/components/engine/docs/sources/reference/builder.md index d3560de718..230c706f12 100644 --- a/components/engine/docs/sources/reference/builder.md +++ b/components/engine/docs/sources/reference/builder.md @@ -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