Hanging containers after stopping selenoid

[Koilanetroc]

Hi,
When I stop selenoid by ./cm selenoid stop it doesn't stop working containers created by that selenoid. Those containers remain hanging and waiting for nothing forever.
Is it a bug or I should handle residual containers on my own?

[vania-pooh]

@Koilanetroc cm currently stops Selenoid this with --force flag and so Selenoid has no chance stop browser containers. I think we could implement --graceful flag that will wait for Selenoid \ Selenoid UI to stop correctly.