Description
Describe the bug
When running Supabase for the first time, it creates a projectname that is invalid and will not allow any actions in Docker Desktop. I assume it is because I have an uppercase letter in my Windows name as the default config.toml
uses that.
Supabase containers still run normally and can be manually shutdown. Trying to shut them all down at once with the project does not work.
To Reproduce
Steps to reproduce the behavior:
- Run
supabase init
- Run
supabase start
- In Docker Desktop, press
Stop
on the project that has been created. - It should give an error along the lines of invalid projectname.
Expected behavior
It should attempt to shutdown all containers
Desktop:
- OS: Windows 11 23H2
- Version of CLI: 1.112.0
- Docker Desktop: v4.25.1
Additional context
I was following the guide on https://supabase.com/docs/guides/cli/getting-started?platform=windows
The default config.toml
created with supabase init
should not have an invalid name based on current Windows user's name. It should probably be something like project_id = "supabase"
Editing the I jumped the gun as it instead will be stuck in a shutting down state. I'm not that well-versed in Docker yetproject_id
to supabase
before running supabase start
will fix the issue.