Error Status 502 when running supabase start

[aidan-wood-43]

Describe the bug Following an update to the CLI, I am no longer able to start supabase services via the cli.

I am using Ubuntu 22.04 via Windows 11 WSL. I initially installed supabase via dpkg with the instructions here. Following this, I ran supabase init, start, etc. as expected without issues. After using supbase cli for a period of time, I was prompted to update the cli. To make this easier, I decided to uninstall the cli installed via source and re-install via npm. Following this, I am now unable to run supabase start without encountering Error status 502:.

The final lines of the error trace are below:

Stopping containers...
Pruned containers: [...]
Pruned volumes: [supabase_db_project_name supabase_storage_project_name supabase_config_project_name  supabase_inbucket_project_name ]
Pruned network: [supabase_network_project_name ]
Error status 502:

As part of efforts to resolve the issue I have attempted the following without success:

• uninstall/reinstall supabase cli via npm
• uninstall/reinstall via brew
• remove all docker containers, networks, and volumes

To Reproduce Steps to reproduce the behavior:

1. Install supabase from source via dpkg
2. Run supabase init, supabase start
3. Uninstall supabase-cli
4. install supabase via npm
5. Run supabase start

Expected behavior I would expect my supabase local instance to be available through localhost.

Screenshots N/A

System information Rerun the failing command with --create-ticket flag.

• Ticket ID: 570f37188b87413a8f38fdc2492df413
• Version of OS: Ubuntu 22.04.2 LTS
• Version of CLI: 1.219.2
• Version of Docker: Docker Engine 24.0.6
• Versions of services:

    SERVICE IMAGE      │      LOCAL       │ LINKED
  ─────────────────────────┼──────────────────┼─────────
  supabase/postgres      │ 15.1.1.78        │ -
  supabase/gotrue        │ v2.163.2         │ -
  postgrest/postgrest    │ v12.2.0          │ -
  supabase/realtime      │ v2.30.34         │ -
  supabase/storage-api   │ v1.11.13         │ -
  supabase/edge-runtime  │ v1.61.0          │ -
  supabase/studio        │ 20241106-f29003e │ -
  supabase/postgres-meta │ v0.84.2          │ -
  supabase/logflare      │ 1.4.0            │ -
  supabase/supavisor     │ 1.1.56           │ -

Additional context If applicable, add any other context about the problem here.

• Version of supabase-js unknown
• Version of Node.js v22.6.0.

[avallete]

Hey there !

Thanks for reporting.

Did you tried cleaning up your local volumes and made sure all containers were down with npx supabase stop --all --no-backup ?

Could you try to run things with the --debug flags to get more details about which container is failing to spin up ?