Guillaume Lours

Hello @Millio345 Can you test with [Docker engine version `25.0.3`](https://github.com/moby/moby/releases/tag/v25.0.3) to check if this is not something already fixed?

@Millio345 @mariaa144 we bumped the version of compose-go yesterday into the main branch of Compose with a fix about networks order & priority, can you check if the [latest binary...

@nulian can you test this [version](https://github.com/docker/compose/actions/runs/7994137875/artifacts/1264074044), we want to be sure the issue will be resolved in the next Compose release

Hey @nocive @dave-shawley Can both of you share the result of `docker compose version`? I wanted to be sure you don't have a old version of Compose taking precedence to...

@nocive you're on linux? No Docker Desktop for Linux installed? Can you try [this Compose binary](https://github.com/docker/compose/actions/runs/7994145230/artifacts/1264075516) and let me know if you see a difference

@nocive strange 🤔 Can you try to use a sample from the awesome-compose or a very simple compose project with only few services, and re-run the `docker compose ps` from...

Yeah 🎉 Thanks @ndeloof for taking care of this when I was away 🙏🤗

It looks like you're reaching the [telemetry timeout](https://github.com/docker/compose/blob/ac8ea082a113327905f88604dfd6b8daca7fc8b1/cmd/cmdtrace/cmd_span.go#L107), I suspect something on the DD side, @milas did improvements on Docker Desktop side but they aren't merged ATM. Next time this...

Hello @LoSunny Do you have the same issue when using `docker build`? Did you check your proxy is well configured to work with Docker? You can check the documentation [here](https://docs.docker.com/network/proxy/)....

Hello @8ma10s Compose watch wasn't designed for this kind of use cases, it expects, at least, to managed different paths for each service so it can apply a dedicated strategy....