© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
SupabaseS
Supabase•4mo ago•
13 replies
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
npx supabase start
, but i seem to frequently get this or similar errors, which makes me have to restart my whole computer
Supabase banner
SupabaseJoin
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
45,816Members
Resources
Was this page helpful?

Similar Threads

Recent Announcements

Similar Threads

Starting with Supabase
SupabaseSSupabase / help-and-questions
5w ago
Supabase CLI not starting up
SupabaseSSupabase / help-and-questions
2mo ago
Having trouble importing Supabase on Swift
SupabaseSSupabase / help-and-questions
6mo ago
supabaseKey property is now private from SupabaseClient
SupabaseSSupabase / help-and-questions
3y ago