Trying to start Docker when it's already started but unresponsive

[nicolasgarnil]

Expected behavior

If Docker is already started but unresponsive, it should not be tried to be started indefinitely

Actual behavior

Docker is being tried to be started indefinitely

Information

When Docker is unresponsive, running docker info usually returns Error response from daemon: Bad response from Docker engine:

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc., v0.9.1)
  compose: Docker Compose (Docker Inc., v2.12.1)
  dev: Docker Dev Environments (Docker Inc., v0.0.3)
  extension: Manages Docker extensions (Docker Inc., v0.2.13)
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc., 0.6.0)
  scan: Docker Scan (Docker Inc., v0.21.0)

Server:
ERROR: Error response from daemon: Bad response from Docker engine
errors pretty printing info

In this case, Docker is considered to be stopped because the server returns an error string. But it isn't, so trying to start it doesn't affect it.

But when it's stopped, docker info returns ERROR: Cannot connect to the Docker daemon.

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc., v0.9.1)
  compose: Docker Compose (Docker Inc., v2.12.1)
  dev: Docker Dev Environments (Docker Inc., v0.0.3)
  extension: Manages Docker extensions (Docker Inc., v0.2.13)
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc., 0.6.0)
  scan: Docker Scan (Docker Inc., v0.21.0)

Server:
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
errors pretty printing info