Nicolas De loof

I can't guarantee this is the actual cause for this issue, just has the same symptoms. [3a4f077](https://github.com/golang/go/commit/3a4f077710b96ee72fcd4214280a41a7c355205b) is part of Go 1.25 Release Candidate, but Docker Compose still relies on...

As Compose v5.0.0 has been release, Docker Compose does not support an internal builder implementation and always delegates to Bake. I'm closing this issue as "not planned" as Compose v5+...

This approach won't work as containers logs will interfere with the `Stop` progress status

Closing this PR as we merged https://github.com/docker/compose/pull/13010

Tried to reproduce, I get the expected `Resource is still in use` warning message and no extra error, not sure what can trigger this

This isn't the same issue as #11387 as here this is the docker engine reporting error: `Error response from daemon: network swarm-overlay not found` Can you please confirm you can...

@kulpsin `docker network ls` indeed does not detect overlay networks created on another swarm node (not sure about the reason, but that's what we get with the engine API) until...

@tuxthepenguin84 docker compose does some client-side validation before running containers, and as such looks for target network to exist. `docker run` will just fail if not found, without preliminary validation....

@tuxthepenguin84 could you please give binary from https://github.com/docker/compose/pull/12233 a try (binaries available on https://github.com/docker/compose/actions/runs/11513518822, at bottom) ? This adds some debugs to the network resolution logic that will help diagnose...

Tested with latest release: Ran DinD "nodes" to simulate a swarm cluster: ``` $ docker run -it --privileged --rm -e DOCKER_TLS_CERTDIR="" -p 50000:2375 --name swarm1 docker:dind .. $ docker run...