Comment 4 for bug 1719045

Let me add 2 more symptoms:

1) dockerd can exit due to SIGSEGV. The issue does NOT always happen: after such a failure, sometimes a retry can succeed.

# systemctl start docker; systemctl status docker
Job for docker.service failed because a fatal signal was delivered to the control process. See "systemctl status docker.service" and "journalctl -xe" for details.
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: failed (Result: signal) since Mon 2017-09-25 23:22:04 UTC; 4ms ago
     Docs: https://docs.docker.com
  Process: 24853 ExecStart=/usr/bin/dockerd -H fd:// $DOCKER_OPTS (code=killed, signal=SEGV)
 Main PID: 24853 (code=killed, signal=SEGV)

Sep 25 23:22:02 decui-u-nested systemd[1]: Starting Docker Application Container Engine...
Sep 25 23:22:02 decui-u-nested dockerd[24853]: time="2017-09-25T23:22:02.027039570Z" level=info msg="libcontainerd: new containerd process, pid: 24867"
Sep 25 23:22:04 decui-u-nested systemd[1]: docker.service: Main process exited, code=killed, status=11/SEGV
Sep 25 23:22:04 decui-u-nested systemd[1]: Failed to start Docker Application Container Engine.
Sep 25 23:22:04 decui-u-nested systemd[1]: docker.service: Unit entered failed state.
Sep 25 23:22:04 decui-u-nested systemd[1]: docker.service: Failed with result 'signal'.

2) "code=exited, status=2"

# systemctl start docker; systemctl status docker

Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2017-09-25 23:32:37 UTC; 5ms ago
     Docs: https://docs.docker.com
  Process: 26237 ExecStart=/usr/bin/dockerd -H fd:// $DOCKER_OPTS (code=exited, status=2)
 Main PID: 26237 (code=exited, status=2)

Sep 25 23:32:37 decui-u-nested dockerd[26237]: runtime.gcBgMarkWorker(0xc82001e000)
Sep 25 23:32:37 decui-u-nested dockerd[26237]: /usr/lib/go-1.6/src/runtime/mgc.go:1433 +0x25f fp=0xc820483fb8 sp=0xc820483f40
Sep 25 23:32:37 decui-u-nested dockerd[26237]: runtime.goexit()
Sep 25 23:32:37 decui-u-nested dockerd[26237]: /usr/lib/go-1.6/src/runtime/asm_amd64.s:1998 +0x1 fp=0xc820483fc0 sp=0xc820483fb8
Sep 25 23:32:37 decui-u-nested dockerd[26237]: created by runtime.gcBgMarkStartWorkers
Sep 25 23:32:37 decui-u-nested dockerd[26237]: /usr/lib/go-1.6/src/runtime/mgc.go:1330 +0x92
Sep 25 23:32:37 decui-u-nested systemd[1]: docker.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Sep 25 23:32:37 decui-u-nested systemd[1]: Failed to start Docker Application Container Engine.
Sep 25 23:32:37 decui-u-nested systemd[1]: docker.service: Unit entered failed state.
Sep 25 23:32:37 decui-u-nested systemd[1]: docker.service: Failed with result 'exit-code'.

It looks the issues are more likely caused by dockerd itself.