Closing one of two Kitematic windows signals shutdown for all containers and Docker VBox VM

[vivace-io]

Expected behavior

Kitematic should not signal with SIGTERM if there exists as second window or instance running already.

Actual behavior

SIGTERM is sent to all running containers.

Information about the Issue

I am using VBox as the Docker host for Kitematic on Windows 10 when I experience this issue, with two or more containers running. More specifically, I am using the official latest stable versions for MongoDB and Redis (not that it makes a great deal of difference in this case).

Steps to reproduce the behavior

1. Launch one instance of Kitematic and use VBox as the Docker host.
2. Start desired containers. In my use case, I had a MongoDB container and a Redis container running.
3. Start a second instance of Kitematic "accidentally."
4. Close the accidental instance of Kitematic.
5. Watch your containers be signaled for shutdown, followed by the entire Docker host VM.

(Possibly) Related Issues

The following are possibly related issues, but I felt mine was different enough that it warranted creating a separate issue.

• 1369 "VBox VM won't shutdown on Kitematic shutdown"

• 1666 "VM keeps running after kitematic closing"

• 532 "Need more badass failure recovery options"

• 851 "Kitematic does not handle daemon restarts / hiccups gracefully"

[FrenchBen]

@vivace-io Thanks for the report - How did you get 2 window open? On my Mac I can only have 1 open.