Nicolas De loof

@silently just tested with V2: ```console $ docker compose --profile test --profile toto up -d [+] Running 5/5 ⠿ Container truc-toto-1 Running 0.0s ⠿ Container truc-toto-2 Running 0.0s ⠿ Container...

Actually, using compose v2, you can easily address both use-cases: [x] stop and remove only services that are enabled - i.e. have no explicit profile assigned `docker compose --profile xxx...

I plan to experiment extending `--remove-orphans` so it includes services created by profile, that is disabled when later running `compose up`

`x-*` syntax is actually used by the Compose Specification to let Compose implementations define custom extensions (like `x-aws-cluster` for ECS deployment). Is there any reason you use `x-volumes` in this...

Are you able to build this same Dockerfile when buildkit is enabled? i.e. run `DOCKER_BUILDKIT=1 docker build .`

ok, could you please attach your `requirements.txt` so we get a reproduction scenario and can transfert this issue to the buildkit team?

Can't reproduce :'(

You could use `docker compose --profile "*" ` to run command with all services enabled

profile have been designed to allow declaration of some optional resources, that should not be enabled by default. If you want a service to be part of the "default" profile,...

ok, so the root cause for asking this is "up still does not respect depends_on and recreate dependent containers in the correct order". Did you opened an issue for this?