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

add a documentation note on backslash usage in shell form of RUN

Browse Source 
Signed-off-by: Amen Belayneh <amenbelayneh@gmail.com>
This commit is contained in:
Amen Belayneh 2015-09-12 15:26:14 +08:00 committed by Tibor Vass
parent d204132ee6
commit 0ece7ed9d4
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/reference/builder.md
View File

@ -311,6 +311,12 @@ commands using a base image that does not contain `/bin/sh`.
> If you want shell processing then either use the *shell* form or execute > If you want shell processing then either use the *shell* form or execute
> a shell directly, for example: `RUN [ "sh", "-c", "echo", "$HOME" ]`. > a shell directly, for example: `RUN [ "sh", "-c", "echo", "$HOME" ]`.
> **Note**:
> If you choose to use the *shell* form, any time you want to continue a single
> `RUN` instruction onto the next line, it has to be ended with a backslash `\`.
> For example, `RUN /bin/bash -c 'source $HOME/.bashrc ;\` then on the next
> line ` echo $HOME '`.
The cache for `RUN` instructions isn't invalidated automatically during The cache for `RUN` instructions isn't invalidated automatically during
the next build. The cache for an instruction like the next build. The cache for an instruction like
`RUN apt-get dist-upgrade -y` will be reused during the next build. The `RUN apt-get dist-upgrade -y` will be reused during the next build. The