Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

supabase db reset intermittently fails: temporary Realtime init job races with the running Realtime service on "schema_migrations_pkey"

未关闭
  • 哪里不对？
#6,915 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@7ttp 已经在做这个了。

开始于 2026年9月30日。

评估

这个 Issue 还没有评估数据。

描述

🐛 Bug supabase/cli

CLI version: 2.118.0 (Linux, Docker Engine, self-hosted GitHub Actions runner), Postgres 17 local stack.

Describe the bug

supabase db reset (local) fails intermittently at the "Initialising schema" stage with error running container: exit 1. It happens mostly on the second reset of a CI job, when the stack has been running for a while. With --debug, the output of the temporary Realtime init container shows:

Resetting local database...
Recreating database...
Initialising schema...
+ echo 'Running migrations'
+ sudo -E -u nobody /app/bin/migrate
** (Ecto.ConstraintError) constraint error when attempting to insert struct:

    * "schema_migrations_pkey" (unique_constraint)
...
    (ecto_sql 3.14.0) lib/ecto/migrator.ex:337: anonymous fn/6 in Ecto.Migrator.async_migrate_maybe_in_transaction/7
error running container: exit 1

Why it happens (reading internal/db/reset/reset.go and internal/db/start/start.go at v2.118.0)

resetDatabase15:

  1. removes and recreates the db container and volume;
  2. runs SetupLocalDatabase → initSchema15, which runs one-off containers for Realtime (/app/bin/migrate, seeds, health_check), Storage (migrate-call.js) and GoTrue (gotrue migrate);
  3. only then calls restartServices (storage, gotrue, realtime, pooler).

During step 2, the persistent supabase_realtime_<project> container is still running against the freshly recreated database. When it restarts itself (it loses its DB connection while the db container is recreated), its entrypoint runs the same Realtime migrations concurrently with the one-off init job. Both insert the same version into _realtime.schema_migrations, and the one-off job crashes on schema_migrations_pkey.

Workaround

Stop the persistent Realtime container before supabase db reset (docker stop supabase_realtime_<project>). restartServices starts it again at the end.

Suggested fix

In resetDatabase15, stop the service containers that run their own migrations (at least Realtime; probably Storage and GoTrue too) before recreating the database, and start them again in restartServices. Alternatively, run the one-off init jobs only while those services are stopped.

To reproduce

  1. supabase start with Realtime enabled (default config).
  2. Run supabase db reset --debug and, as soon as it prints Initialising schema..., run docker restart supabase_realtime_<project>. This simulates the service restarting on its own after losing the database.
  3. The reset fails with the error above. The same sequence with the Realtime container stopped beforehand succeeds.

Observed locally (CLI 2.118.0, 2026-09-30):

  • Realtime running and restarted at Initialising schema...: 1 of 3 resets failed with the exact error above; the one-off Realtime container was the only one that exited 1.
  • Realtime stopped before the reset: 3 of 3 succeeded, and restartServices left it running.
  • Plain resets (control): 2 of 2 succeeded.
主要语言
TypeScript
星标
2.4k
派生
537
平均合并
21 小时 24 分钟
30 天内合并 PR
378

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

supabase/cli 的其他 Issue

查看 supabase/cli 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。