-
Notifications
You must be signed in to change notification settings - Fork 249
[Bug] Cant run supabase locally because supabase_vector fails #3404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi! I have the same problem
Os: Windows 11 |
@sweatybridge - As mentioned 👍 |
@jonathanstiansen usually its caused by the socket's is not listening, i think there's something wrong with the setup/config, maybe its not hitting the rancher server
i thinks its somewhat similar to this issue: linkerd/linkerd2#12688 |
Bug report
There was one issue talked about in discussions.
Describe the bug
When I type
supabase start
or reset, or anything and thenstart
it never starts the vector container - therefore never starts supabase locallyTo Reproduce
npm install -g supabase # Using Homebrew (macOS) brew install supabase/tap/supabase supabase init supabase start
Expected behavior
Supabase should run locally
System information
shouldn't have anything to do with node since it's a container running
The text was updated successfully, but these errors were encountered: