Nicolas De loof

In an ideal world the engine (or nvidia driver) would manage this as a pool of resources, just like you can declare a service to bind port with a range,...

I wonder you could rely on CDI (https://github.com/docker/compose/pull/12184) so that you don't need to explicitly assign a device ID to a container, but can request a device by CDI specification...

Docker Compose indeed fully parse and resolve your compose file before it execute any command, and doing so will detect missing env file whenever this isn't used by the `pull`...

@danieletorelli which image are you using to reproduce ?

@danieletorelli I tried to reproduce with homeassistant image. ``` $ docker compose up -d [+] Running 33/33 ✔ serviceA Pulled 97.0s [+] Running 2/2 ✔ Network truc_default Created 0.0s ✔...

if `docker inspect ` fails, that seems to demonstrate a docker engine issue with some resource "dead locked". > If you remove the second port in stack2, it also works...

@danieletorelli please report to github.com/moby/moby. Whenever there might be something wrong with Compose, engine should not crash as client API is somehow misused. cc @thaJeztah

@pbering I'm not saying there's nothing wrong with Compose and we can't provide a fix, but if you see Docker engine stuck, this demonstrates an issue on engine side which...

`--index` applies to containers created by `up` command. When you target containers created by `run` it has no effect, as such container as not indexed. Flag _should_ be rejected to...

According to heap dump it seems opentelemetry is not correctly used in Docker Compose and we leak spans not being collected. The only related change I can fine between [compose...