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 suppose when starting application with docker compose -f compose.yaml -f local.yaml up interpolation happens before merging compose files.
Since that if compose.yaml has required environment variable which must be overrode by local.yaml, docker compose up will fail.
My expectation: docker compose up will be applied to config from docker compose -f compose.yaml -f local.yaml config --no-interpolate.
Steps To Reproduce
Compose files:
#compose.yamlservices:
postgres:
image: postgresenvironment:
POSTGRES_USER: ${PG_USER?PG_USER must be set}POSTGRES_PASSWORD: ${PG_PASSWORD?PG_PASSWORD must be set}POSTGRES_DB: ${PG_DB?PG_DB must be set}
Earlier attempt to fix this issue introduced significant regression. I guess with current compose-go architecture we as stuck with this limitation. This will be considered if we eventually start working on next-gen compose architecture, but for now there's no such plan.
Description
I suppose when starting application with
docker compose -f compose.yaml -f local.yaml up
interpolation happens before merging compose files.Since that if
compose.yaml
has required environment variable which must be overrode bylocal.yaml
,docker compose up
will fail.My expectation:
docker compose up
will be applied to config fromdocker compose -f compose.yaml -f local.yaml config --no-interpolate
.Steps To Reproduce
Compose files:
Merged config with no interpolation (which is what I want)
docker compose -f .\compose.yaml -f .\local.yaml config --no-interpolate
:What I get with
docker compose -f compose.yaml -f local.yaml up
:Compose Version
Docker Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: