mirror of
https://github.com/moby/moby.git
synced 2022-11-09 12:21:53 -05:00
Merge pull request #9957 from crosbymichael/envars
Specify ENV variables are also used for CMD.
This commit is contained in:
commit
11e47996dc
2 changed files with 4 additions and 2 deletions
|
@ -120,7 +120,8 @@ or
|
|||
**ENV**
|
||||
--**ENV <key> <value>**
|
||||
The ENV instruction sets the environment variable <key> to
|
||||
the value <value>. This value is passed to all future RUN instructions. This is
|
||||
the value <value>. This value is passed to all future
|
||||
RUN, ENTRYPOINT, and CMD instructions. This is
|
||||
functionally equivalent to prefixing the command with **<key>=<value>**. 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
|
||||
|
|
|
@ -349,7 +349,8 @@ accessible from the host by default. To expose ports to the host, at runtime,
|
|||
ENV <key>=<value> ...
|
||||
|
||||
The `ENV` instruction sets the environment variable `<key>` to the value
|
||||
`<value>`. This value will be passed to all future `RUN` instructions. This is
|
||||
`<value>`. This value will be passed to all future
|
||||
`RUN`, `ENTRYPOINT`, and `CMD` instructions. This is
|
||||
functionally equivalent to prefixing the command with `<key>=<value>`
|
||||
|
||||
The `ENV` instruction has two forms. The first form, `ENV <key> <value>`,
|
||||
|
|
Loading…
Add table
Reference in a new issue