A docker resource fails when pacemaker probes the resources at cluster startup

Issue

• A docker resource is throwing "unknown error" during a startup probe.
• ocf:heartbeat:docker resource reports successful stop after error communicating with daemon.

# pcs status | grep "Failed Actions" -A 10
Failed Actions:
* rabbitmq-bundle-docker-2_monitor_0 on controller-0 'unknown error' (1): call=15, status=complete, exitreason='',
    last-rc-change='Wed Sep 12 00:27:56 2018', queued=0ms, exec=970ms
* galera-bundle-docker-0_monitor_0 on controller-0 'unknown error' (1): call=19, status=complete, exitreason='',
    last-rc-change='Wed Sep 12 00:27:57 2018', queued=0ms, exec=738ms
* redis-bundle-docker-1_monitor_0 on controller-0 'unknown error' (1): call=38, status=complete, exitreason='',
    last-rc-change='Wed Sep 12 00:28:10 2018', queued=0ms, exec=792ms
* haproxy-bundle-docker-1_monitor_0 on controller-0 'unknown error' (1): call=75, status=complete, exitreason='',
    last-rc-change='Wed Sep 12 00:28:19 2018', queued=0ms, exec=366ms
* openstack-cinder-volume-docker-0_monitor_0 on controller-0 'unknown error' (1): call=83, status=complete, exitreason='',
    last-rc-change='Wed Sep 12 00:28:25 2018', queued=0ms, exec=349ms