From 1be6e4c9798c6a19ed946a154ed71642e7322b24 Mon Sep 17 00:00:00 2001 From: magentaqin Date: Sun, 30 Nov 2025 19:26:59 +0100 Subject: [PATCH 1/2] chore(docs): mention Docker requirement for db pull --- docs/supabase/db/pull.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/supabase/db/pull.md b/docs/supabase/db/pull.md index 8f20f0b8f..7d3234be0 100644 --- a/docs/supabase/db/pull.md +++ b/docs/supabase/db/pull.md @@ -4,6 +4,9 @@ Pulls schema changes from a remote database. A new migration file will be create Requires your local project to be linked to a remote database by running `supabase link`. For self-hosted databases, you can pass in the connection parameters using `--db-url` flag. +> **Note** +> This command requires Docker Desktop (or a running Docker daemon), as it starts a local Postgres container to diff your remote schema. + Optionally, a new row can be inserted into the migration history table to reflect the current state of the remote database. If no entries exist in the migration history table, `pg_dump` will be used to capture all contents of the remote schemas you have created. Otherwise, this command will only diff schema changes against the remote database, similar to running `db diff --linked`. From 5230a1b89fa26169b83c1476ddb9a3324975ae70 Mon Sep 17 00:00:00 2001 From: Han Qiao Date: Mon, 1 Dec 2025 11:37:17 +0800 Subject: [PATCH 2/2] Clarify Docker requirement in pull.md Updated note about Docker requirement for the pull command. --- docs/supabase/db/pull.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/supabase/db/pull.md b/docs/supabase/db/pull.md index 7d3234be0..1f9f4ae66 100644 --- a/docs/supabase/db/pull.md +++ b/docs/supabase/db/pull.md @@ -4,8 +4,7 @@ Pulls schema changes from a remote database. A new migration file will be create Requires your local project to be linked to a remote database by running `supabase link`. For self-hosted databases, you can pass in the connection parameters using `--db-url` flag. -> **Note** -> This command requires Docker Desktop (or a running Docker daemon), as it starts a local Postgres container to diff your remote schema. +> Note this command requires Docker Desktop (or a running Docker daemon), as it starts a local Postgres container to diff your remote schema. Optionally, a new row can be inserted into the migration history table to reflect the current state of the remote database.