Nicolas De loof

I'm looking into this. Sorry for the inconvenience, we use stale bot as we get many issues reported but never get an update from reported after we ask for more...

AFAICT the root cause for this issue is that `docker compose exec` runs interactive _by default_, while `docker exec` requires an explicit `-i`. Doing so, you have `compose` and `less`...

`build` command relies on Bake since v2.40, which **requires** an actual console to render build UI with colored/animated output. Maybe we should detect this requirement mismatch and let Bake run...

@shanesmith you can set BUILDKIT_DISPLAY=plain (after https://github.com/docker/compose/pull/13455 has been released) to get Compose UI being colored, but build rendered as plain text

@derlin a bug-fix release is planned later this week

@snyh can't reproduce ``` >tmp docker compose -f test.yaml up [+] Running 2/0 ✔ Network tmp_default Created 0.0s ✔ Container tmp-test-1 Created 0.0s Attaching to test-1 test-1 exited with code...

I can't reproduce your issue: ``` $ docker compose stop web [+] Stopping 1/1 ✔ Container avatars-web-1 Stopped 0.3s $ docker compose ps --status=running --format json {"Command":"\"flask run --host=0.…\"","CreatedAt":"2024-05-17 08:08:30...

please inspect stopped container (`docker inspect 625..`) and attach output

IIUC you have `docker-compose.hosts.yml` set to "just" define a `hosts` attribute you want to reuse in other services ? So, basically, you'd like to have support for yaml anchors from...

While _feasible_, such a feature would make the compose parser way more complex to manage the many overrides paths. Ability to "define fragments of configuration" is already well supported with...