Docker-DCO-1.1-Signed-off-by: Sven Dowideit <SvenDowideit@docker.com> (github: SvenDowideit)
| ... | ... |
@@ -313,8 +313,9 @@ beginning user will then be forced to learn about `ENTRYPOINT` and |
| 313 | 313 |
`--entrypoint`. |
| 314 | 314 |
|
| 315 | 315 |
In order to avoid a situation where commands are run without clear visibility |
| 316 |
-to the user, make sure your script ends with something like `exec "$@"`. After |
|
| 317 |
-the entrypoint completes, the script will transparently bootstrap the command |
|
| 316 |
+to the user, make sure your script ends with something like `exec "$@"` (see |
|
| 317 |
+[the exec builtin command](http://wiki.bash-hackers.org/commands/builtin/exec)). |
|
| 318 |
+After the entrypoint completes, the script will transparently bootstrap the command |
|
| 318 | 319 |
invoked by the user, making what has been run clear to the user (for example, |
| 319 | 320 |
`docker run -it mysql mysqld --some --flags` will transparently run |
| 320 | 321 |
`mysqld --some --flags` after `ENTRYPOINT` runs `initdb`). |