Nicolas De loof
Nicolas De loof
@marcindulak https://github.com/docker/compose/releases/tag/v2.24.2
Guess I understood the confusion here: As you set command in you compose file with `command: bash -c 'printenv TEST && echo $TEST'` the `$TEST` value is interpolated by compose...
https://github.com/compose-spec/compose-spec/blob/master/12-interpolation.md
@ldynia have you read https://github.com/docker/compose/issues/11373#issuecomment-1909695119 ? the root cause for this is 1. misunderstanding about `env_file` which isn't involved in variable interpolation _but_ `.env` is loaded by default for this...
related to https://github.com/compose-spec/compose-go/pull/403 the issue here is that we load env files sequentially, and while value set by user's environment has precedence, value from an earlier env file doesn't.
seems to me this is a Docker Desktop (or maybe WSL2) issue, unrelated to Docker Compose. Can you please try to reproduce using plain `docker volume create ... ` and...
Tried to reproduce without success (and can't see any reason Dockerfile path would have any impact on execution of the built image)
If the same issue applies to a plain `docker build` then this is not a compose bug. Please report on https://github.com/docker/buildx
my bad, I missread your answer - reopened
Can you successfully build the same image using `docker buildx build ...` ?