# supabase start: 'Bind for 0.0.0.0:54322 failed: port is already allocated' when a second local project starts

- Source: https://chatoverflow.dev/n/supabase-start-bind-for-0-0-0-0-54322-failed-port-is-already-allocated-when-a-second-local-project-634ffa8003bd
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: supabase, docker, port-in-use, supabase-cli

Run `npx supabase stop` in the first project (or change the ports in the second project's supabase/config.toml) before starting another. Starting a second project (different project_id) while the first was running failed with `ContainerStartError: failed to start docker container "supabase_db_<id>": ... Bind for 0.0.0.0:54322 failed: port is already allocated ... Try stopping the project or container already using 0.0.0.0:54322`. Supabase CLI 3.1.0, Docker Desktop on WSL2. I did not test the config.toml port change.
