[BUG] Command illa doctor doesn't work on MacOS

[domderen]

Describe the bug
Hey, I cloned this repo, installed dependencies, built the project and tried running the doctor subcommand. I got an information that No running docker found even though I have docker installed & running.

To Reproduce
Steps to reproduce the behavior:

1. Clone the repo
2. Inside the repo dir, run cargo run -- doctor
3. See an error

Expected behavior
I would expect the doctor subcommand to detect docker on my machine.

Screenshots

Desktop (please complete the following information):

• OS: MacOS Sonoma 14.0 (23A344)
• Docker version 24.0.6 installed via Docker Desktop

Additional context
Full docker info log:

 $ docker info
Client:
 Version:    24.0.6
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.11.2-desktop.5
    Path:     /Users/dominikderen/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.22.0-desktop.2
    Path:     /Users/dominikderen/.docker/cli-plugins/docker-compose
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/dominikderen/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.20
    Path:     /Users/dominikderen/.docker/cli-plugins/docker-extension
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v0.1.0-beta.8
    Path:     /Users/dominikderen/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /Users/dominikderen/.docker/cli-plugins/docker-sbom
  scan: Docker Scan (Docker Inc.)
    Version:  v0.26.0
    Path:     /Users/dominikderen/.docker/cli-plugins/docker-scan
  scout: Docker Scout (Docker Inc.)
    Version:  v1.0.7
    Path:     /Users/dominikderen/.docker/cli-plugins/docker-scout

Server:
 Containers: 28
  Running: 3
  Paused: 0
  Stopped: 25
 Images: 49
 Server Version: 24.0.6
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 8165feabfdfe38c65b599c4993d227328c231fca
 runc version: v1.1.8-0-g82f18fe
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.4.16-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 16
 Total Memory: 6.784GiB
 Name: docker-desktop
 ID: b10b28d8-e296-4ac9-9514-17819097415a
 Docker Root Dir: /var/lib/docker
 Debug Mode: true
  File Descriptors: 68
  Goroutines: 89
  System Time: 2023-10-31T12:46:38.608889353Z
  EventsListeners: 11
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: daemon is not using the default seccomp profile

[domderen]

This seems to be related to an issue inside the bollard::Docker dependency. Some details are provided in this issue.

A working fix is to set DOCKER_HOST environment variable to unix:///Users/<your_user_name>/.docker/run/docker.sock