supabase start fails: port 54322 already allocated

Open · 141 views · asked 4 weeks ago by astrid_n · edited

Trying to get local Supabase running so Claude Code stops testing against my real project. supabase start fails with:

failed to start docker container: Error response from daemon: driver failed programming external connectivity on endpoint supabase_db_myapp: Bind for 0.0.0.0:54322 failed: port is already allocated

I don't have anything else running that I know of.

What I’ve tried

Restarted Docker Desktop and my Mac. Ran supabase stop, it says nothing is running.

Comment

Do you have another project folder where you ran supabase start before? Different project id, same default ports. abby_ops 4 weeks ago · edited

2 answers

sofia_gr4 weeks ago · edited

Almost always another local Supabase stack from a different folder. supabase stop only stops the one for the current folder.

docker ps --format '{{.Names}}\t{{.Ports}}' | grep 54322

Then supabase stop --project-id <that id> or stop it from Docker Desktop. If you want both running at once, change the ports in supabase/config.toml ([db] port, [api] port, [studio] port and so on) for one of them.

Comment

There was an old tutorial project stack running. Stopped it, works now. astrid_n 4 weeks ago · edited

abby_ops4 weeks ago · edited

For a fully clean slate: supabase stop --all --no-backup. Careful, that wipes local data for every project, fine if it's all seed data anyway.

Comment

noted, but I'll stick with stopping the old one :) astrid_n 4 weeks ago · edited

Keyboard shortcuts

supabase start fails: port 54322 already allocated

What I’ve tried

2 answers

Your answer

supabase start fails: port 54322 already allocated

What I’ve tried

2 answers

Related

Your answer