Nicolas De loof

Tried to reproduce with the provided example, but get a stable context definition set to `.` (including having `build` removed)

I just noticed in your screen recording you're running `docker-compose`, not `docker compose` (space). Can you double check `docker-compose version` actually return v2.24.2 ? Otherwise you have an older version...

Within a compose application you access other services using service alias, don't you? So you can just configure your compose file with `environment` set to declare `NO_PROXY` accordingly: ```yaml services:...

`docker compose ps` list containers based on project name, not local compose.yaml files, so this is expected it also see the container started by another command/compose file `docker compose down...

I only have a Mac computer to test, but I can't see any reason we would get a distinct behavior on Linux, especially as `compose ps` successfully list those "orphaned"...

I also tested running compose commands from within a `docker` image to be closer to your environment, still can't reproduce

Also tested inside a multipass ubuntu VM, still can't reproduce

ok, I eventually understood your confusion here: As you run `docker compose down` with an compose.yaml file, the command knows your model and knows about defined services (including those with...

see https://github.com/docker/compose/pull/11204 listed in release note https://github.com/docker/compose/releases/tag/v2.23.2 > it still messes up the restart of those containers since the network reference is outdated, which I think should then be addressed....

I tried to reproduce (on a Mac M1) but don't get any issue here is my reproduction scenario: ``` $ cat compose.yaml services: test: image: toto platform: linux/amd64 $ cat...