Skip to content
Get a quote

Supabase CLI errorSupabase CLI: supabase start can’t connect to the Docker daemon

Cannot connect to the Docker daemon is the error supabase start shows when no container runtime is running. The local Supabase stack runs in Docker containers, so Docker Desktop, OrbStack or a compatible tool must be installed and started first.

Short answer

Open Docker Desktop or OrbStack and wait until it is running, then run supabase start again. If you use Colima or Podman, point DOCKER_HOST at its socket. If another local project holds the ports, run supabase stop there first.

Rather not fix it yourself? App Fix Ticket starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.

Why supabase start can’t reach Docker, and the fix

  1. 01

    No container runtime is running

    “A container manager compatible with Docker APIs is a prerequisite for supabase start” Supabase docs, Local development

    Installing the CLI doesn’t install Docker. Install a runtime, start it, and check with docker ps before supabase start.

  2. 02

    The CLI looks at the wrong socket

    Colima, Podman and Rancher Desktop use their own socket paths. Set DOCKER_HOST to that socket in the shell where you run the CLI. The sample is Colima’s default; run docker context ls to find the path for other tools.

    export DOCKER_HOST="unix://$HOME/.colima/default/docker.sock"
supabase start

  3. 03

    Another local project holds the ports

    “With the default ports, supabase start runs one local project per machine.” Supabase docs, Running multiple local projects

    Also check: a second project with the default config.toml clashes with the first. This shows a port conflict rather than the daemon error. Run supabase stop in the other project, or change its ports.

  4. 04

    The first start looks stuck

    “The first run takes time while the CLI downloads the Docker images.” Supabase docs, Supabase CLI

    The first run downloads the whole stack as images. Give it time and free disk space before you cancel it.

Checked against the vendor’s docs on : Supabase docs: Local development; Supabase docs: Supabase CLI; Supabase docs: Running multiple local projects.

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

“Very responsive, attentive to fixing bugs, and completed the project as needed! Thank you!”
A buyer in the United States, July 2022. Shopify on Fiverr
All 127 Fiverr reviews

Related: Supabase migration failed (db push) · Supabase staging environment · Supabase too many connections · Supabase PGRST200

Questions

More on this error

Which container tool should I use on a Mac?

Supabase recommends OrbStack on macOS, and Docker Desktop on Windows and Linux. Rancher Desktop and Podman also work.

Can I run Supabase locally without Docker?

The experimental supabase stack commands can run services as processes on Linux and Apple silicon Macs. For most projects, Docker is still the simpler path.

Can you fix it for me?

If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.

A different error?

Describe it and get a written quote

Send the error and what you were doing. You get a written scope, a fixed price and a timeline; Simon replies by email, usually within one business day.

Describe your problem All fixes