docker rm -fed containers linger

[rade]

seen with scope 0.13...

docker rm -f <C>ing a containers linger in the UI for 20s. Not always - @2opremio can reproduce this quite reliably on a single machine, but I only see it when running the app on my desktop and the probe in a VM.

I've also observed this for short-lived containers started with --rm.

By contrast docker kill <C>; docker rm <C> removes the container from the UI immediately, so does docker kill <C> on its own.

[2opremio]

There's a race calling InspectContainer() when containers are rmed. The inspection fails because the container doesn't exist anymore and then we simply delete the container from the Probe's state without notifying the App.