Nicolas De loof

Noticed something weird : ``` $ docker compose -f overlay.yaml down -v [+] Running 3/3 ✔ Container truc-nginx-1 Removed 0.2s ✔ Network second-net Removed 0.2s ! Network net Resource is...

If such a feature exists on Bake (github.com/docker/buildx) we would add support for it. AFAICT build process doesn't ket you select a container runtime but offers platform abstraction to achieve...

Closing as "not planned" - compose only can expose features supported by the builder.

compose returned 1 as some container exited. `docker compose up -d --wait` expect services to be **running** and healthy

unfortunately: no. Compose doesn't (yet) have an explicit concept for "jobs" which are expected to exit.

interpolation works for sure, in most cases confusion comes from setting values based on env file, and how those get loaded with some default paths. > Different settings handle interpolation...

> The other two syntaxes do not work in a reliable/predictable fashion. Please provide an illustration example so I can confirm this is a bug or explain / propose docs...

@yakobe `env_file` is **not** used to process compose.yaml and interpolate variables, but to set containers environment. see https://docs.docker.com/compose/how-tos/environment-variables/set-environment-variables/ which isn't the same as https://docs.docker.com/compose/how-tos/environment-variables/variable-interpolation/ I'm closing this issue as there's...

Can you please try running `docker buildx bake -f compose.yaml` to double check buildx is correctly installed and can build your application ? Can also check: ``` docker compose build...

Maybe related to https://github.com/golang/go/issues/73170, to be fixed in go 1.25