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
I'd like to rewrite the value of environmental variable using multiple compose files mechanism, which worked perfectly in 1.29, but seems like a bug in v2.
Steps to reproduce the issue:
Simple two files example. Compose files are intentionally minified to focus on the issue.
While this makes perfect sense this behavior unfortunately was undocumented.
I've created compose-spec/compose-spec#284 so we can get this a canonical approch
Description
I'd like to rewrite the value of environmental variable using multiple compose files mechanism, which worked perfectly in 1.29, but seems like a bug in v2.
Steps to reproduce the issue:
Simple two files example. Compose files are intentionally minified to focus on the issue.
v1 overrides the env value, but v2 not.
Describe the results you received:
FOO_ENDPOINT
value is taken fromdocker-compose.yml
Describe the results you expected:
FOO_ENDPOINT
would benull
(a value from override compose file)Additional information you deem important (e.g. issue happens only occasionally):
—
Output of
docker compose version
:Output of
docker info
:Additional environment details:
—
The text was updated successfully, but these errors were encountered: