Difference in behavior from docker-compose and docker compose (stop)

[dellagustin-sap]

Description of the issue

For a compose file where services describe depenendencies (i.e. service-b declares a dependes_on dependency on service-a, docker-compose stop service-b will only stop service-b, while docker compose stop service-b will stop both services, service-a and service-b, this is a breaking change and there is no flag (to my best knowledge) that allows the usage with the same behavior as docker-compose.

Context information (for bug reports)

Output of docker-compose version

docker-compose version 1.29.0, build 07737305
docker-py version: 5.0.0
CPython version: 3.9.0
OpenSSL version: OpenSSL 1.1.1h  22 Sep 2020

Output of docker version

Docker version 20.10.5, build 55c4c88

Output of docker-compose config
(Make sure to add the relevant -f and other flags)

(paste here)

Steps to reproduce the issue

1. start a service-b that depends on a service-a with docker compose up
2. stop the service-b with docker compose stop service-b

Observed result

service-a is also stopped.

Expected result

only service-b should be stopped

Stacktrace / full error message

(paste here)

Additional information

Docker for Mac, macOS version 11.4

[ndeloof]

This issue has been fixed already by #1577
Plase check latest release https://github.com/docker/compose-cli/releases/tag/v2.0.0-beta.3

[dellagustin-sap]

Thank you!