From 7f1ea7129e7b87e60ea4b1e4449b0541f6f432c9 Mon Sep 17 00:00:00 2001 From: Sven Dowideit Date: Fri, 24 Oct 2014 12:41:19 +1000 Subject: [PATCH] Add a link to some documentation about exec. Docker-DCO-1.1-Signed-off-by: Sven Dowideit (github: SvenDowideit) --- docs/sources/articles/dockerfile_best-practices.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/sources/articles/dockerfile_best-practices.md b/docs/sources/articles/dockerfile_best-practices.md index 31f932d651..c403c2f286 100644 --- a/docs/sources/articles/dockerfile_best-practices.md +++ b/docs/sources/articles/dockerfile_best-practices.md @@ -313,8 +313,9 @@ beginning user will then be forced to learn about `ENTRYPOINT` and `--entrypoint`. 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, `docker run -it mysql mysqld --some --flags` will transparently run `mysqld --some --flags` after `ENTRYPOINT` runs `initdb`).