Per Bering

> 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,...

@danieletorelli sorry for the slight delay, I've just tested with latest Docker Desktop v4.41.2 which has engine v28.1.1 and compose v2.35.1-desktop.1 and the behavior is the same unfortunately.

@danieletorelli ... almost the the behavior, it does **not** print `exit status 130` anymore when trying to abort the hanging up command.

Did the test again on latest Docker Desktop 4.46.0 with Compose 2.39.2-desktop.1 and Engine 28.4.0, still the same issue and the only way to recover is to reboot machine.