From 80d7165cfb758791ccef8fa765d65f3199fa97c1 Mon Sep 17 00:00:00 2001 From: unknown Date: Fri, 30 Aug 2024 17:44:51 +0530 Subject: [PATCH] (Fix) Interpolation documentation of env is misleading Fixes #20735 --- .../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 b95690e9ffa5..dcf18ce24a61 100644 --- a/content/compose/environment-variables/set-environment-variables.md +++ b/content/compose/environment-variables/set-environment-variables.md @@ -82,7 +82,7 @@ The paths to your `.env` file, specified in the `env_file` attribute, are relati ### Additional information - If multiple files are specified, they are evaluated in order and can override values set in previous files. -- In addition, as the `.env` file supports [interpolation](variable-interpolation.md), it is possible to combine those with values set by `environment`. +- The variable interpolation supported by the [.env file](variable-interpolation.md), is explicitly not available to env files specified using `env_file`. - As of Docker Compose version 2.24.0, you can set your `.env` file, defined by the `env_file` attribute, to be optional by using the `required` field. When `required` is set to `false` and the `.env` file is missing, Compose silently ignores the entry. ```yaml env_file: