Skip to content

Takes COMPOSE_PROJECT_NAME into consideration on commands#9332

Merged
ulyssessouza merged 1 commit intodocker:v2from
ulyssessouza:fix-project-name
Mar 31, 2022
Merged

Takes COMPOSE_PROJECT_NAME into consideration on commands#9332
ulyssessouza merged 1 commit intodocker:v2from
ulyssessouza:fix-project-name

Conversation

@ulyssessouza
Copy link
Contributor

What I did
Take COMPOSE_PROJECT_NAME into consideration on commands

Related issue
Resolves #9316

@ulyssessouza ulyssessouza requested review from glours and ndeloof March 31, 2022 12:27
Signed-off-by: Ulysses Souza <ulyssessouza@gmail.com>
Copy link
Contributor

@glours glours left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ulyssessouza ulyssessouza merged commit 5e63f12 into docker:v2 Mar 31, 2022
hotzevzl added a commit to Vizzuality/marxan-cloud that referenced this pull request May 6, 2022
This being make, the original implementation caused the value of the
make variable COMPOSE_PROJECT_NAME to _include the surrounding
double-quotes_, and this _happened_ to work just because we were using
this variable in shell commands, where the quoting would be handled as
normal CLI quoting of a string. However, since we _also_ make this make
variable available as environment variable (through the `export` command
through which we set env vars from a dotenv file), this ended up
breaking things from Compose v2.4 through this change:
docker/compose#9332.
hotzevzl added a commit to Vizzuality/marxan-cloud that referenced this pull request May 6, 2022
This being make, the original implementation caused the value of the
make variable COMPOSE_PROJECT_NAME to _include the surrounding
double-quotes_, and this _happened_ to work just because we were using
this variable in shell commands, where the quoting would be handled as
normal CLI quoting of a string. However, since we _also_ make this make
variable available as environment variable (through the `export` command
through which we set env vars from a dotenv file), this ended up
breaking things from Compose v2.4 through this change:
docker/compose#9332.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

COMPOSE_PROJECT_NAME causing "no configuration file provided: not found" in logs command

2 participants