Browse Source

Add a link to some documentation about exec.

Docker-DCO-1.1-Signed-off-by: Sven Dowideit <SvenDowideit@docker.com> (github: SvenDowideit)
Sven Dowideit 10 years ago
parent
commit
7f1ea7129e
1 changed files with 3 additions and 2 deletions
  1. 3 2
      docs/sources/articles/dockerfile_best-practices.md

+ 3 - 2
docs/sources/articles/dockerfile_best-practices.md

@@ -313,8 +313,9 @@ beginning user will then be forced to learn about `ENTRYPOINT` and
 `--entrypoint`.
 `--entrypoint`.
 
 
 In order to avoid a situation where commands are run without clear visibility
 In order to avoid a situation where commands are run without clear visibility
-to the user, make sure your script ends with something like `exec "$@"`. After
-the entrypoint completes, the script will transparently bootstrap the command
+to the user, make sure your script ends with something like `exec "$@"` (see
+[the exec builtin command](http://wiki.bash-hackers.org/commands/builtin/exec)).
+After the entrypoint completes, the script will transparently bootstrap the command
 invoked by the user, making what has been run clear to the user (for example,
 invoked by the user, making what has been run clear to the user (for example,
 `docker run -it mysql mysqld --some --flags` will transparently run
 `docker run -it mysql mysqld --some --flags` will transparently run
 `mysqld --some --flags` after `ENTRYPOINT` runs `initdb`).
 `mysqld --some --flags` after `ENTRYPOINT` runs `initdb`).