From e3007c51a5b9b144adc4dc716e3b62ca27dd4ad2 Mon Sep 17 00:00:00 2001 From: Vincent Demeester Date: Tue, 17 May 2016 17:06:12 +0200 Subject: [PATCH] Merge pull request #22768 from mansinahar/run-cmd-doc Update 'run' command doc for better readability. Issue:#22721 (cherry picked from commit 28a436af3641f202287f98e326537a10897da9fa) Signed-off-by: Sebastiaan van Stijn --- docs/reference/commandline/run.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/reference/commandline/run.md b/docs/reference/commandline/run.md index 97553a67dc..544aa37240 100644 --- a/docs/reference/commandline/run.md +++ b/docs/reference/commandline/run.md @@ -227,12 +227,12 @@ system's interfaces. This sets simple (non-array) environmental variables in the container. For illustration all three flags are shown here. Where `-e`, `--env` take an environment variable and -value, or if no `=` is provided, then that variable's current value is passed -through (i.e. `$MYVAR1` from the host is set to `$MYVAR1` in the container). -When no `=` is provided and that variable is not defined in the client's -environment then that variable will be removed from the container's list of -environment variables. -All three flags, `-e`, `--env` and `--env-file` can be repeated. +value, or if no `=` is provided, then that variable's current value, set via +`export`, is passed through (i.e. `$MYVAR1` from the host is set to `$MYVAR1` +in the container). When no `=` is provided and that variable is not defined +in the client's environment then that variable will be removed from the +container's list of environment variables. All three flags, `-e`, `--env` and +`--env-file` can be repeated. Regardless of the order of these three flags, the `--env-file` are processed first, and then `-e`, `--env` flags. This way, the `-e` or `--env` will