Intermittent "Container id not available for service database - has it been started?" about gradle-dcompose-plugin HOT 2 OPEN

Not really sure, what the problem is here... the only thing that seems weird to me is:
You are defining the task testI inside the DcomposeExtension block... I'm not really sure, if that might have any side-effects...

The error message itself seems like the task graph is not being executed in the expected order. Could you add some more console log output, where I can see a) the execution order of the tasks and b) which task threw this error?

from gradle-dcompose-plugin.

The testI is declared elsewhere, in DcomposeExtension I'm just configuring it with systemPropertys and adding the dependencies.
The failure looks like this:

> Task :myProject:mySubprojectA:stopDatabaseContainer
> Task :myProject:mySubprojectA:removeDatabaseContainer
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':myProject:mySubprojectB:startDatabaseContainer'.
> Container id not available for service database - has it been started?

So execution order seems to be fine.
Additionally, sometimes failure doesn't happen at all, sometimes it happens in a random subprojeсt.
Also, upgraded gradle to 7.2, made no difference.

from gradle-dcompose-plugin.