S
Supabase•4d ago
skeddles

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.
i first opened docker desktop, then ran npx supabase start, but i seem to frequently get this or similar errors, which makes me have to restart my whole computer
8 Replies
skeddles
skeddlesOP•4d ago
okay nevermind i guess... i closed docker and then ran the command again and it worked. i just really dont understand docker
inder
inder•4d ago
error message says you have another container with same name already present.
skeddles
skeddlesOP•4d ago
but what does that mean? I didn't create any containers, everything that exists is just done by the cli tool and idk why that would change a minute later
inder
inder•4d ago
could be some issue with docker, resolved a minute later you can see the running containers in docker-desktop or run docker ps
skeddles
skeddlesOP•4d ago
do you generally open docker desktop first before trying to start it?
inder
inder•4d ago
yes you need to start docker-desktop first because that launches docker engine
skeddles
skeddlesOP•3d ago
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-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 same thing happens when i try to do supabase db reset, it just hangs forever same with start... is there something i can do other than restarting my entire computer?
inder
inder•3d ago
First take down all the containers and remove all supabase volumes. Then run supabase start and see if all containers are healthy

Did you find this page helpful?