Supabase CLI 2.122.0 prunes local Docker network before database container creation on Windows/WSL2
维护者通常 1 天内回复
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 42/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- docker, postgresql, typescript
调研方向
Start by locating the supabase start flow and Docker network creation, cleanup, and database container startup paths; compare them with the related issue #6136. Determine whether the project-filtered prune request comes from CLI cleanup or overlapping processes, then identify a reproducible way to preserve the network through startup. Done means the database container attaches and the local stack starts without the network being pruned.
由索引模型根据 Issue 内容生成。
描述
Affected area
Local development
Supabase CLI version
v2.122.0
Operating system
Windows 10 Pro 22H2 (Build 19045.7807), WSL2 3.0.1.0
Installation method
GitHub release binary
Command
supabase start
Actual output
Local Supabase startup failed because the project's Docker network was removed before the database container started.
Error:
network supabase_network_<local-project-id> not found
Docker API event timeline (UTC, October 26, 2026):
- 23:58:32.881 — Project network created
- 23:58:33.231 — Database volume created
- 23:58:35.587 — POST /v1.56/networks/prune, filtered by the local Supabase project label
- 23:58:36.634 — Project network destroyed
- 23:58:37.029 — Database container created referencing the deleted network
Docker API user agent: Docker-Client/29.9.2 (windows).
The Docker Engine did not restart. No application SQL or migrations were executed. The process responsible for the prune request has not been conclusively identified.
Expected behavior
The Supabase CLI should preserve the project's Docker network while creating and starting the PostgreSQL, Auth, and PostgREST containers.
The database container should attach successfully to the project network, and the local stack should start without an unexpected project-network deletion.
Steps to reproduce
- Install Supabase CLI 2.122.0 on Windows 10 with Docker Desktop using the WSL2 backend.
- Initialize a fresh isolated local project using
supabase init. - Configure local-only URLs, the
publicData API schema, and disable automatic migrations and seed execution. - Confirm Docker Desktop is running with the
desktop-linuxcontext. - Run
supabase start. - Observe the Docker network and container lifecycle events.
Observed: the project network was created and then pruned before the database container started.
This occurred during one observed startup attempt. Reproduction across repeated attempts has not been established.
Crash report ID
No response
Docker and service versions
Docker Desktop: 4.97.0 (244584)
Docker Client: 29.9.2
Docker Engine: 29.9.2
Docker API: 1.56
Docker context: desktop-linux
Server OS/Architecture: linux/amd64
containerd: 2.4.2
runc: 1.5.2
WSL version: 3.0.1.0
WSL default version: 2
Supabase CLI: 2.122.0
Local Supabase services did not become healthy. PostgreSQL, Auth, and PostgREST were not started successfully.
Additional context
The failure appears to involve a project-filtered Docker network-prune request occurring during startup.
The exact calling process is unknown. The timing is consistent with a Supabase CLI cleanup path or overlapping CLI processes, but neither is confirmed.
No Docker Engine restart, custom firewall configuration, or unrelated scheduled network-pruning service was identified.
Related issue: https://github.com/supabase/cli/issues/6136
That issue differs because PostgreSQL became healthy before cleanup. In this case, the project network was destroyed before database container startup.
No hosted Supabase project, production database, credentials, or customer records were involved.
Please advise whether this is a known cleanup-order/concurrency issue and whether an officially supported workaround or patched release is available.
- 主要语言
- TypeScript
- 星标
- 2.4k
- 派生
- 537
- 平均合并
- 18 小时 2 分钟
- 30 天内合并 PR
- 387
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
supabase/cli 的其他 Issue
-
db schema declarative sync: no way to fail (non-zero exit) when the generated migration is destructive可能重新可做 关联的 PR 已关闭且未合并。 未关闭✨ Feature supabase/cli
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
Windows: Supabase CLI start fails when no Supabase containers exist可能已有人在做 @Coly010 于 1 天前认领。 未关闭🐛 Bug supabase/cli
难度 3/5 1-2 天 新手友好度 35/100
维护者通常 1 天内回复
-
🐛 Bug supabase/cli
难度 4/5 3-5 天 新手友好度 48/100
维护者通常 1 天内回复
-
stack: every Edge Function request starts a new worker, so the same function never reuses one and each call pays a cold start可能已有人在做 @7ttp 于 2 天前认领。 未关闭🐛 Bug supabase/cli
难度 3/5 1-2 天 新手友好度 58/100
维护者通常 1 天内回复
-
🐛 Bug supabase/cli
难度 4/5 3-5 天 新手友好度 48/100
维护者通常 1 天内回复
相似的 Issue
-
fix(worker): keep normal prepare waiting states failure-free可能已有人在做 @LichKing-2234 今天认领。 未关闭agent:codex priority:P1
难度 2/5 1-3 小时 新手友好度 72/100
AgoraIO-Extensions/agent-infra#3745 ·
维护者通常 1 天内回复
-
The five-line work window can drop its oldest line: the per-line byte share ignores the JSON framing可能已有人在做 @Eapp1e 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 84/100
makecindy/cindy#7973 · 1 条评论 ·
维护者通常 1 天内回复
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
难度 1/5 1 小时以内 新手友好度 78/100
lingdojo/kana-dojo#33337 · 1 条评论 · 5 个 reaction ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
code-yeongyu/senpi#4917 · 1 条评论 ·
维护者通常 1 天内回复