trouble starting supabase

i seem to have trouble starting the docker container every time i restart my computer

> vite-react-template-skeddles@0.0.0 supabase-start
> npx supabase start

Starting database from backup...
Starting containers...
WARNING: Analytics on Windows requires Docker daemon exposed on tcp://localhost:2375. 
See https://supabase.com/docs/guides/local-development/cli/getting-started?queryGroups=platform&platform=windows#running-supabase-locally for more details.
Stopping containers...
failed to create docker container: Error response from daemon: Conflict. The container name "/supabase_vector_portfolio.quest" is already in use by container "a3f7ee9d88d3eaada0c8881c329d568074956b2b801439fe0256e39b94f9c911". You have to remove (or rename) that container to be able to reuse that name.
Try rerunning the command with --debug to troubleshoot the error.

 *  The terminal process "C:\Windows\System32\cmd.exe /d /c npm run supabase-start" terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it. 

 *  Executing task: npm run supabase-status 


> vite-react-template-skeddles@0.0.0 supabase-status
> npx supabase status

failed to inspect container health: Error response from daemon: No such container: supabase_db_portfolio.quest
Try rerunning the command with --debug to troubleshoot the error.

 *  The terminal process "C:\Windows\System32\cmd.exe /d /c npm run supabase-status" terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it.

> vite-react-template-skeddles@0.0.0 supabase-start
> npx supabase start

Starting database from backup...
Starting containers...
WARNING: Analytics on Windows requires Docker daemon exposed on tcp://localhost:2375. 
See https://supabase.com/docs/guides/local-development/cli/getting-started?queryGroups=platform&platform=windows#running-supabase-locally for more details.
Stopping containers...
failed to create docker container: Error response from daemon: Conflict. The container name "/supabase_vector_portfolio.quest" is already in use by container "a3f7ee9d88d3eaada0c8881c329d568074956b2b801439fe0256e39b94f9c911". You have to remove (or rename) that container to be able to reuse that name.
Try rerunning the command with --debug to troubleshoot the error.

 *  The terminal process "C:\Windows\System32\cmd.exe /d /c npm run supabase-start" terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it. 

 *  Executing task: npm run supabase-status 


> vite-react-template-skeddles@0.0.0 supabase-status
> npx supabase status

failed to inspect container health: Error response from daemon: No such container: supabase_db_portfolio.quest
Try rerunning the command with --debug to troubleshoot the error.

 *  The terminal process "C:\Windows\System32\cmd.exe /d /c npm run supabase-status" terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it.

> vite-react-template-skeddles@0.0.0 supabase-start
> npx supabase start

Starting database from backup...
Starting containers...
WARNING: Analytics on Windows requires Docker daemon exposed on tcp://localhost:2375. 
See https://supabase.com/docs/guides/local-development/cli/getting-started?queryGroups=platform&platform=windows#running-supabase-locally for more details.
Stopping containers...
failed to create docker container: Error response from daemon: Conflict. The container name "/supabase_vector_portfolio.quest" is already in use by container "a3f7ee9d88d3eaada0c8881c329d568074956b2b801439fe0256e39b94f9c911". You have to remove (or rename) that container to be able to reuse that name.
Try rerunning the command with --debug to troubleshoot the error.

 *  The terminal process "C:\Windows\System32\cmd.exe /d /c npm run supabase-start" terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it. 

 *  Executing task: npm run supabase-status 


> vite-react-template-skeddles@0.0.0 supabase-status
> npx supabase status

failed to inspect container health: Error response from daemon: No such container: supabase_db_portfolio.quest
Try rerunning the command with --debug to troubleshoot the error.

 *  The terminal process "C:\Windows\System32\cmd.exe /d /c npm run supabase-status" terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it.

> vite-react-template-skeddles@0.0.0 supabase-start
> npx supabase start

Starting database from backup...
Starting containers...
WARNING: Analytics on Windows requires Docker daemon exposed on tcp://localhost:2375. 
See https://supabase.com/docs/guides/local-development/cli/getting-started?queryGroups=platform&platform=windows#running-supabase-locally for more details.
Stopping containers...
failed to create docker container: Error response from daemon: Conflict. The container name "/supabase_vector_portfolio.quest" is already in use by container "a3f7ee9d88d3eaada0c8881c329d568074956b2b801439fe0256e39b94f9c911". You have to remove (or rename) that container to be able to reuse that name.
Try rerunning the command with --debug to troubleshoot the error.

 *  The terminal process "C:\Windows\System32\cmd.exe /d /c npm run supabase-start" terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it. 

 *  Executing task: npm run supabase-status 


> vite-react-template-skeddles@0.0.0 supabase-status
> npx supabase status

failed to inspect container health: Error response from daemon: No such container: supabase_db_portfolio.quest
Try rerunning the command with --debug to troubleshoot the error.

 *  The terminal process "C:\Windows\System32\cmd.exe /d /c npm run supabase-status" terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it.

i first opened docker desktop, then ran

npx supabase start

npx supabase start

npx supabase start

npx supabase start, but i seem to frequently get this or similar errors, which makes me have to restart my whole computer

skeddlesOP•10/17/25, 2:05 PM

okay nevermind i guess... i closed docker and then ran the command again and it worked.
i just really dont understand docker

inder•10/17/25, 2:05 PM

error message says you have another container with same name already present.

skeddlesOP•10/17/25, 2:06 PM

but what does that mean? I didn't create any containers, everything that exists is just done by the cli tool

skeddlesOP•10/17/25, 2:07 PM

and idk why that would change a minute later

inder•10/17/25, 2:07 PM

could be some issue with docker, resolved a minute later

inder•10/17/25, 2:07 PM

you can see the running containers in docker-desktop or run docker psdocker ps

skeddlesOP•10/17/25, 2:08 PM

do you generally open docker desktop first before trying to start it?

inder•10/17/25, 2:08 PM

yes you need to start docker-desktop first because that launches docker engine

skeddlesOP•10/17/25, 8:07 PM

now im having trouble trying to back up my database (because i need to do a reset after a migration but i dont want all the data deleted)

but when i try to do supabase db dump --data-onlysupabase db dump --data-only it says

Initialising login role...
Dumping data from remote database...

Initialising login role...
Dumping data from remote database...

and then hangs forever until i cancel it.

and now if i try to do supabase status, it says this:

Y:\Projects\Websites\portfolio.quest>npx supabase status --debug
open supabase\.temp\profile: The system cannot find the file specified.
Supabase CLI 2.51.0
Using profile: supabase (supabase.co)
supabase_db_portfolio.quest container is not ready: unhealthy

Y:\Projects\Websites\portfolio.quest>npx supabase status --debug
open supabase\.temp\profile: The system cannot find the file specified.
Supabase CLI 2.51.0
Using profile: supabase (supabase.co)
supabase_db_portfolio.quest container is not ready: unhealthy

maybe because i ran supabase link? i thought i had to do db dump, but it seems like im linking it to my live project and not my local one...

I just dont understand docker

skeddlesOP•10/17/25, 8:42 PM

same thing happens when i try to do supabase db reset, it just hangs forever

skeddlesOP•10/17/25, 9:03 PM

same with start... is there something i can do other than restarting my entire computer?

Sskeddles same with start... is there something i can do other than restarting my entire c...

inder•10/18/25, 5:55 AM

First take down all the containers and remove all supabase volumes.

inder•10/18/25, 5:56 AM

Then run supabase startsupabase start and see if all containers are healthy

trouble starting supabase

Similar Threads

Similar Threads

Similar Threads