-
Notifications
You must be signed in to change notification settings - Fork 357
Open
Description
Describe the bug
I can't stop + start supabase without running into this error. To be fair I don't know what I'm doing, but it seems like this is supposed to work. I have to delete the container manually after every stop.
To Reproduce
- pnpm add supabase --save-dev --allow-build=supabase
- supabase start --network-id localnet
- supabase stop
- supabase start --network-id localnet
failed to create docker container: Error response from daemon: Conflict. The container name "/supabase_vector_supabase" is already in use by container "(hex)". You have to remove (or rename) that container to be able to reuse that name.
System information
Rerun the failing command with --create-ticket flag.
- Version of OS: Windows 10
- Version of CLI: 2.72.8
- Version of Docker: 29.1.3, build f52814d
- Versions of services:
supabase/postgres | 17.6.1.072 | -
supabase/gotrue | v2.185.0 | -
postgrest/postgrest | v14.3 | -
supabase/realtime | v2.70.0 | -
supabase/storage-api | v1.33.5 | -
supabase/edge-runtime | v1.70.0 | -
supabase/studio | 2026.01.12-sha-4e9b718 | -
supabase/postgres-meta | v0.95.2 | -
supabase/logflare | 1.28.0 | -
supabase/supavisor | 2.7.4 | -
Metadata
Metadata
Assignees
Labels
No labels