From a431b1dda6b3c67df82c7266efb992c28fa198ee Mon Sep 17 00:00:00 2001 From: Per Lundberg Date: Fri, 1 Dec 2023 15:30:07 +0200 Subject: [PATCH] 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 --- docs/reference/commandline/exec.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/reference/commandline/exec.md b/docs/reference/commandline/exec.md index ccc0b3f3d0..c9656b7ecd 100644 --- a/docs/reference/commandline/exec.md +++ b/docs/reference/commandline/exec.md @@ -77,10 +77,10 @@ This starts a new shell session in the container `mycontainer`. Next, set environment variables in the current bash session. -By default, the `docker exec` command, inherits the environment variables that -are set at the time the container is created. Use the `--env` (or the `-e` shorthand) -to override global environment variables, or to set additional environment variables -for the process started by `docker exec`. +The `docker exec` command inherits the environment variables that are set at the +time the container is created. Use the `--env` (or the `-e` shorthand) to +override global environment variables, or to set additional environment +variables for the process started by `docker exec`. 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.