From 1f0a72e010535761c22ffd048367e1e9a23b804e Mon Sep 17 00:00:00 2001 From: Jan Koprowski Date: Mon, 15 Dec 2014 13:28:42 +0100 Subject: [PATCH] Specify ENV variables are also used for CMD. Signed-off-by: Michael Crosby Upstream-commit: 66387aee5970a9b100f0d14612d7b7726eaf7b9d Component: engine --- components/engine/docs/man/Dockerfile.5.md | 3 ++- components/engine/docs/sources/reference/builder.md | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/components/engine/docs/man/Dockerfile.5.md b/components/engine/docs/man/Dockerfile.5.md index 0114f30ba7..9d6f6c8159 100644 --- a/components/engine/docs/man/Dockerfile.5.md +++ b/components/engine/docs/man/Dockerfile.5.md @@ -120,7 +120,8 @@ or **ENV** --**ENV ** The ENV instruction sets the environment variable to - the value . This value is passed to all future RUN instructions. This is + the value . This value is passed to all future + RUN, ENTRYPOINT, and CMD instructions. This is functionally equivalent to prefixing the command with **=**. The environment variables that are set with ENV persist when a container is run from the resulting image. Use docker inspect to inspect these values, and diff --git a/components/engine/docs/sources/reference/builder.md b/components/engine/docs/sources/reference/builder.md index 90862334ef..73af35c6ff 100644 --- a/components/engine/docs/sources/reference/builder.md +++ b/components/engine/docs/sources/reference/builder.md @@ -349,7 +349,8 @@ accessible from the host by default. To expose ports to the host, at runtime, ENV = ... The `ENV` instruction sets the environment variable `` to the value -``. This value will be passed to all future `RUN` instructions. This is +``. This value will be passed to all future +`RUN`, `ENTRYPOINT`, and `CMD` instructions. This is functionally equivalent to prefixing the command with `=` The `ENV` instruction has two forms. The first form, `ENV `,