From 2dee6b5ecbd9703fe94bd60c190c87f366a1e4e9 Mon Sep 17 00:00:00 2001 From: Jonathan Sharpe Date: Mon, 19 Feb 2024 08:31:41 +0000 Subject: [PATCH] Fix incorrect reference to "up -e" (fixes #18965) (#19427) --- .../compose/environment-variables/set-environment-variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/compose/environment-variables/set-environment-variables.md b/content/compose/environment-variables/set-environment-variables.md index 149e9f215b..6a5e25c5a5 100644 --- a/content/compose/environment-variables/set-environment-variables.md +++ b/content/compose/environment-variables/set-environment-variables.md @@ -80,7 +80,7 @@ services: - You can place your `.env` file in a location other than the root of your project's directory, and then use one of the following methods so Compose can navigate to it: - The [`--env-file` option in the CLI](#substitute-with---env-file) - Using the [`env_file` attribute in the Compose file](../compose-file/05-services.md#env_file) -- Values in your `.env` file can be overridden from the command line by using [`docker-compose up -e`](#set-environment-variables-with-docker-compose-run---env). +- Values in your `.env` file can be overridden from the command line by using [`docker compose run -e`](#set-environment-variables-with-docker-compose-run---env). - Your `.env` file can be overridden by another `.env` if it is [substituted with `--env-file`](#substitute-with---env-file). > **Important**