French Ben
French Ben
@westfood no real consequence, except you don't know if docker is still alive on the machine. The idea behind the ELB check, was to confirm that our docker diagnose container...
Seems like this is similar to: https://github.com/docker/swarmkit/issues/1340
@shazChaudhry it's a bit more complicated than that - When you restart the engine, there's also a very high chance you'll trigger an instance health-check failure.
@jmaitrehenry thanks for the issue - It's been already updated and will be part of the next release.
@kinghuang the code is in [Infrakit](https://github.com/docker/infrakit/tree/master/pkg/provider/aws/plugin/loadbalancer), feel free to suggest how this could be done, and I'll be happy to patch it :)
Are you able to provide some details of what was running on the box prior to the crash, so that we can replicate it here. Additionally, if you're able to...
You can run the exact command from the docs. `kill -SIGUSR1 $(pidof dockerd)` It doesn't look like it, but `pidof` is a proper program: ``` $ pidof --help BusyBox v1.26.2...
Since you're logged-in to the container shell, you wont have full access to the docker PID and will need to start a privileged container to get that (which you can't,...
@sshorkey the separation has been brought up a few times and something we're looking to provide. I'm not sure the applications being restarted fairly often would be the cause, but...