Update docs: mention Docker requirement for db pull #4553
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Docs update for db pull--add Docker requirement.
What is the current behavior?
The
supabase db pullcommand can fail with: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 pulldocs now include a short note:This should make it clearer for new users that
db pulldepends on a running Docker daemon.This is how it would be rendered:

Additional context
From my understanding, several other
supabase dbsubcommands (e.g.db start,db dump) also rely on Docker to run Postgres orpg_dumpin a container.To keep this PR small and focused, I only updated the
db pulldocs. I’m happy to:supabase dbsection, and/ordbsubcommands in a follow-up PR,if you think that would be helpful.