Nicolas De loof
Nicolas De loof
I confirm compose do search for config file in parent folders (https://github.com/compose-spec/compose-go/blob/master/cli/options.go#L136) Tried to reproduce your issue, but "works for me"
Can you please confirm you get the same issue building this Dockerfile when using `docker buildx build .` (or alternatively `DOCKER_BUILDKIT=1 docker build .`)? Otherwise, this should be reported to...
You can run `DOCKER_BUILDKIT=0 docker compose build` to force use of the "classic" builder, anyway I suggest you report this bug to the [buildx team](https://github.com/docker/buildx)
I'm closing this issue as "not specific to docker compose"
My bad: as I tested on Mac OS, obviously `--env-file=/dev/null` worked, but I eventually got bootcamp setup with Docker Desktop Windows so I can give it a try on Microsoft...
Closing this issue in favor for https://github.com/docker/compose/issues/9181
it's not possible we expose container number (used to name replicas) as a variable as this one is computed as we compare existing vs expected resource, AFTER parsing the compose...
Same issue applies both to Compose v1 and v2 the root cause is that both use a bind mount to "inject" secret inside container, but bind mount doesn't allow a...
> having to rebuild the image to change a secret isn't an option This is not my proposal: compose would copy the secret into the container (not image) after creation,...