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

Cerrado
  • ¿Algo no está bien?
#7,339 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@jgoux ya está trabajando en esto.

Desde el 27/10/2026.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
42/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
docker, postgresql, typescript
Área
cli, databases

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

🐛 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.

Lenguaje dominante
TypeScript
Estrellas
2.4k
Forks
540
Merge medio
17 h 29 min
PR fusionados (30 d)
387

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de supabase/cli

Todos los issues de supabase/cli

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.