You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here we see that ${COMPOSE_PROJECT_NAME} inside the docker-compose.yml file is taken from the environment and overrides the value provided in the .env file.
The problem is that ${COMPOSE_PROJECT_NAME} inside the .env file is not taken from the environment which is inconsistent.
This looks like a bug to me. I think that variable resolution should work identically inside .env and docker-compose.yaml files.
At a very least it should be documented somewhere. I couldn't find any documentation on how variables are resolved inside the .env file.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Description of the issue
Context information (for bug reports)
Output of
docker-compose version
Output of
docker version
Steps to reproduce the issue
.env
file file with the following contents:docker-compose.yml
file with the following contents:COMPOSE_PROJECT_NAME=custom docker-compose config
Observed result
Expected result
Additional information
Here we see that
${COMPOSE_PROJECT_NAME}
inside thedocker-compose.yml
file is taken from the environment and overrides the value provided in the.env
file.The problem is that
${COMPOSE_PROJECT_NAME}
inside the.env
file is not taken from the environment which is inconsistent.This looks like a bug to me. I think that variable resolution should work identically inside
.env
anddocker-compose.yaml
files.At a very least it should be documented somewhere. I couldn't find any documentation on how variables are resolved inside the
.env
file.The text was updated successfully, but these errors were encountered: