From 01b521c002be4fd3f4192a9f226f839ce905bf3d Mon Sep 17 00:00:00 2001 From: Daniel Nephin Date: Wed, 17 Jan 2018 16:55:07 -0500 Subject: [PATCH] Update buidler ENV docs Signed-off-by: Daniel Nephin --- docs/reference/builder.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/reference/builder.md b/docs/reference/builder.md index ed945a7308..1462d5b861 100644 --- a/docs/reference/builder.md +++ b/docs/reference/builder.md @@ -805,14 +805,15 @@ see the ENV = ... The `ENV` instruction sets the environment variable `` to the value -``. This value will be in the environment of all "descendant" -`Dockerfile` commands and can be [replaced inline](#environment-replacement) in +``. This value will be in the environment for all subsequent instructions +in the build stage and can be [replaced inline](#environment-replacement) in many as well. The `ENV` instruction has two forms. The first form, `ENV `, will set a single variable to a value. The entire string after the first -space will be treated as the `` - including characters such as -spaces and quotes. +space will be treated as the `` - including whitespace characters. The +value will be interpreted for other environment variables, so quote characters +will be removed if they are not escaped. The second form, `ENV = ...`, allows for multiple variables to be set at one time. Notice that the second form uses the equals sign (=) @@ -830,8 +831,7 @@ and ENV myDog Rex The Dog ENV myCat fluffy -will yield the same net results in the final image, but the first form -is preferred because it produces a single cache layer. +will yield the same net results in the final image. The environment variables set using `ENV` will persist when a container is run from the resulting image. You can view the values using `docker inspect`, and