Guest24897
/
DockerCLI
mirror of https://github.com/docker/cli.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

exec.md: remove misleading part 

"By default" implies that this is something which could be
disabled for an individual `docker exec` call. This doesn't seem
to be the case, so removing the "by default" part would make
these docs clearer to me.

Signed-off-by: Per Lundberg <per.lundberg@hibox.tv>
(cherry picked from commit a431b1dda6)
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This commit is contained in:
Per Lundberg 2023-12-01 15:30:07 +02:00 committed by Sebastiaan van Stijn
parent 3ab117e7cd
commit a976e5084a
No known key found for this signature in database
GPG Key ID: 76698F39D527CE8C
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/reference/commandline/exec.md
View File

@ -77,10 +77,10 @@ This starts a new shell session in the container `mycontainer`.
Next, set environment variables in the current bash session. Next, set environment variables in the current bash session.
By default, the `docker exec` command, inherits the environment variables that The `docker exec` command inherits the environment variables that are set at the
are set at the time the container is created. Use the `--env` (or the `-e` shorthand) time the container is created. Use the `--env` (or the `-e` shorthand) to
to override global environment variables, or to set additional environment variables override global environment variables, or to set additional environment
for the process started by `docker exec`. variables for the process started by `docker exec`.
The example below creates a new shell session in the container `mycontainer` with The example below creates a new shell session in the container `mycontainer` with
environment variables `$VAR_A` and `$VAR_B` set to "1" and "2" respectively. environment variables `$VAR_A` and `$VAR_B` set to "1" and "2" respectively.