Skip to content
Discussion options

You must be logged in to vote

Hey, I had a similar issue too and found this issues thread detailing the nature of the issue and two workarounds, one needing a configurable local Docker instance of Supabase and another to simply run the cli without vector enabled.
It seems like it's a issue related to the version of vector being used which will have to be fixed in an update to supabase/cli itself. For now, you can try running supabase start -x vector as a workaround if you do not require the vector functionality. Credits to @jweberde and @encima for the fixes and discussion! Hope this helps.

Replies: 4 comments 9 replies

Comment options

You must be logged in to vote
9 replies
@Hael616
Comment options

@maxwelljmckee
Comment options

@mikolertesx
Comment options

@qiao-x
Comment options

@mattiadevivo
Comment options

Answer selected by Vimblin
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet