Skip to content

Conversation

@magentaqin
Copy link
Contributor

What kind of change does this PR introduce?

Docs update for db pull--add Docker requirement.

What is the current behavior?

The supabase db pull command can fail with:

Cannot connect to the Docker daemon at unix:///.../docker.sock. Is the docker daemon running?

when Docker Desktop (or another Docker engine) is not running, but this requirement is not mentioned in the docs.

Related issue: #4507

What is the new behavior?

The supabase db pull docs now include a short note:

This command requires Docker Desktop (or a running Docker daemon), as it starts a local Postgres container to diff your remote schema.

This should make it clearer for new users that db pull depends on a running Docker daemon.

This is how it would be rendered:
Screenshot 2025-11-30 at 19 32 47

Additional context

From my understanding, several other supabase db subcommands (e.g. db start, db dump) also rely on Docker to run Postgres or pg_dump in a container.

To keep this PR small and focused, I only updated the db pull docs. I’m happy to:

  • add a more general note under the top-level supabase db section, and/or
  • update the docs for the other db subcommands in a follow-up PR,

if you think that would be helpful.

@magentaqin magentaqin requested a review from a team as a code owner November 30, 2025 18:33
Updated note about Docker requirement for the pull command.
@sweatybridge sweatybridge merged commit 32175e9 into supabase:develop Dec 1, 2025
13 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants