Nicolas De loof

Such labels indeed will confuse compose as this makes those resources look like they're managed by compose, not `external`, and could explain this issue. Sounds to me network has been...

This should have been fixed by https://github.com/docker/compose/pull/10555 If the issue persist after next release (v2.17.4, to be released soon) feel free to comment or create a follow up issue

Can you please confirm this issue is still relevant with latest release (v2.18.1) ? I guess this is already fixed by https://github.com/compose-spec/compose-go/pull/403

closing this issue as answered by https://github.com/docker/compose/issues/7891#issuecomment-1254549401

@williamdes see https://hub.docker.com/r/docker/compose > Important 📣 Docker Compose is now included as part of the [Docker official image](https://hub.docker.com/_/docker) 🎉 ...

This has been fixed by https://github.com/compose-spec/compose-go/pull/332

@mathieu-lemay as you use `API_KEY: "${API_KEY}"` in your compose file for build.args, you refer to an actual environment variable, not a build arg, so you should run `API_KEY=api-key docker compose...

Tried to reproduce on latest codebase: ``` $ docker-compose --ansi=never up -d db db Pulling 45f14b91a40f Pulling fs layer ... 0b9bf888f4ce Pull complete db Pulled Container engage-db Creating Container engage-db...

Let's close this one as reproduction scenario doesn't help anymore and follow up on this with https://github.com/docker/compose/issues/9600

being able to support this comes with multiple challenges: 1. compose would need to support `dns` being set with a service name. This is the easy part: we could just...