Update 'run' command doc for better readability. Issue:#22721
(cherry picked from commit 28a436af3641f202287f98e326537a10897da9fa)
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
| ... | ... |
@@ -227,12 +227,12 @@ system's interfaces. |
| 227 | 227 |
This sets simple (non-array) environmental variables in the container. For |
| 228 | 228 |
illustration all three |
| 229 | 229 |
flags are shown here. Where `-e`, `--env` take an environment variable and |
| 230 |
-value, or if no `=` is provided, then that variable's current value is passed |
|
| 231 |
-through (i.e. `$MYVAR1` from the host is set to `$MYVAR1` in the container). |
|
| 232 |
-When no `=` is provided and that variable is not defined in the client's |
|
| 233 |
-environment then that variable will be removed from the container's list of |
|
| 234 |
-environment variables. |
|
| 235 |
-All three flags, `-e`, `--env` and `--env-file` can be repeated. |
|
| 230 |
+value, or if no `=` is provided, then that variable's current value, set via |
|
| 231 |
+`export`, is passed through (i.e. `$MYVAR1` from the host is set to `$MYVAR1` |
|
| 232 |
+in the container). When no `=` is provided and that variable is not defined |
|
| 233 |
+in the client's environment then that variable will be removed from the |
|
| 234 |
+container's list of environment variables. All three flags, `-e`, `--env` and |
|
| 235 |
+`--env-file` can be repeated. |
|
| 236 | 236 |
|
| 237 | 237 |
Regardless of the order of these three flags, the `--env-file` are processed |
| 238 | 238 |
first, and then `-e`, `--env` flags. This way, the `-e` or `--env` will |