1berry/docker-cli
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #30329 from johndmulhausen/patch-2

Browse Source 
Fixing formatting errors in Run refdoc

Signed-off-by: Misty Stanley-Jones <misty@docker.com>
This commit is contained in:
Victor Vieux 2017-01-20 14:14:15 -08:00 committed by Tibor Vass
parent ad214d7a79
commit dd05de1e6a
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/reference/builder.md
View File

@ -1286,8 +1286,8 @@ to create the directory in the Dockerfile. For example:
ARG <name>[=<default value>] ARG <name>[=<default value>]
The `ARG` instruction defines a variable that users can pass at build-time to The `ARG` instruction defines a variable that users can pass at build-time to
the builder with the `docker build` command using the `--build-arg the builder with the `docker build` command using the `--build-arg <varname>=<value>`
<varname>=<value>` flag. If a user specifies a build argument that was not flag. If a user specifies a build argument that was not
defined in the Dockerfile, the build outputs a warning. defined in the Dockerfile, the build outputs a warning.
``` ```
@ -1375,7 +1375,7 @@ useful interactions between `ARG` and `ENV` instructions:
``` ```
Unlike an `ARG` instruction, `ENV` values are always persisted in the built Unlike an `ARG` instruction, `ENV` values are always persisted in the built
image. Consider a docker build without the --build-arg flag: image. Consider a docker build without the `--build-arg` flag:
``` ```
$ docker build Dockerfile $ docker build Dockerfile
@ -1638,9 +1638,9 @@ The command invoked by docker will be:
cmd /S /C powershell -command Execute-MyCmdlet -param1 "c:\foo.txt" cmd /S /C powershell -command Execute-MyCmdlet -param1 "c:\foo.txt"
This is inefficient for two reasons. First, there is an un-necessary cmd.exe command This is inefficient for two reasons. First, there is an un-necessary cmd.exe command
processor (aka shell) being invoked. Second, each `RUN` instruction in the *shell* processor (aka shell) being invoked. Second, each `RUN` instruction in the *shell*
form requires an extra `powershell -command` prefixing the command. form requires an extra `powershell -command` prefixing the command.
To make this more efficient, one of two mechanisms can be employed. One is to To make this more efficient, one of two mechanisms can be employed. One is to
use the JSON form of the RUN command such as: use the JSON form of the RUN command such as: