Windows: Supabase CLI start fails when no Supabase containers exist
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- docker, postgresql, powershell, supabase, typescript
Research direction
The failure comes from the start command's container checks and from the profile file read (C:\Users....supabase\profile) that status --debug attempts. Start by reproducing with a fresh init on Windows, then trace where the 'already running' message is produced when the db container is missing. Done means start either brings up the stack or prints the real startup error, and status no longer fails on the missing profile file.
Written by the indexing model from the issue text.
Description
Affected area
Local development
Supabase CLI version
2.122.0
Operating system
Windows 11, PowerShell
Installation method
npm
Command
npx supabase@latest start
npx supabase@latest status --debug
Actual output
NotFound: FileSystem.readFile (C:\Users\Malle\.supabase\profile)
supabase start is already running.
supabase_db_TECHNOMAK-SUPABASE-RECOVERY container is not running:
The same error occurs in a fresh folder initialized with `npx supabase@latest init`. Docker shows no Supabase containers.
Expected behavior
The CLI should start the local Supabase environment successfully, or report the underlying startup error clearly, instead of reporting that the project is already running when its database container is absent.
Steps to reproduce
- On Windows PowerShell, create a fresh folder.
- Run
npx supabase@latest init. - Run
npx supabase@latest start. - Observe the “supabase start is already running” error and missing database container message.
- Run
npx supabase@latest status --debug. - Observe the missing
C:\Users\Malle\.supabase\profileerror.
Environment:
- Supabase CLI 2.122.0
- Docker Engine 29.9.1
- Docker Compose v5.6.0
- Fresh local project, not linked to a hosted project
Crash report ID
No response
Docker and service versions
Additional context
No response
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 540
- Avg merge
- 17h 29m
- Merged PRs (30d)
- 387
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/cli
-
db schema declarative sync: no way to fail (non-zero exit) when the generated migration is destructiveMay be free again A pull request for this issue was closed without being merged. Open✨ Feature supabase/cli
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
`supabase start` waits about 10 seconds for Docker's first health check after services are readyOpen🐛 Bug supabase/cli
Difficulty 3/5 1-2 days Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
🐛 Bug supabase/cli
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
stack: every Edge Function request starts a new worker, so the same function never reuses one and each call pays a cold startPossibly taken @7ttp claimed this 4 days ago. Open🐛 Bug supabase/cli
Difficulty 3/5 1-2 days Newbie friendliness 58/100
supabase/cli#7274 · 1 assignee ·
Maintainers usually reply within 1 day
-
🐛 Bug supabase/cli
Difficulty 4/5 3-5 days Newbie friendliness 48/100
supabase/cli#7269 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
components-web-app/docs#311 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NEARBuilders/everything-dev#678 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
formbricks/formbricks#9881 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day