Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Supabase CLI 2.122.0 prunes local Docker network before database container creation on Windows/WSL2

クローズ
  • 何か問題がありますか？
#7,339 コメント 0 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@jgoux がすでに取り組んでいます。

2026年10月27日 から。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
42/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
docker, postgresql, typescript
領域
cli, databases

調査の方向性

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 の本文から書いたものです。

説明

🐛 Bug supabase/cli
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
  1. Install Supabase CLI 2.122.0 on Windows 10 with Docker Desktop using the WSL2 backend.
  2. Initialize a fresh isolated local project using supabase init.
  3. Configure local-only URLs, the public Data API schema, and disable automatic migrations and seed execution.
  4. Confirm Docker Desktop is running with the desktop-linux context.
  5. Run supabase start.
  6. 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
フォーク
540
平均マージ
17時間 29分
マージ済み PR（30日）
387

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

supabase/cli のほかの issue

supabase/cli の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。