Skip to content
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

Can't start the template project because pgvector not installed in the docker image. #6

Open
PEIslander opened this issue Dec 22, 2024 · 0 comments

Comments

@PEIslander
Copy link

I got the following error message trying to start the memory-agent template.

`Failed to start project memory-agent
info | Setting up vector index
error | Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/starlette/routing.py", line 693, in lifespan
async with self.lifespan_context(app) as maybe_state:
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/contextlib.py", line 210, in aenter
return await anext(self.gen)
^^^^^^^^^^^^^^^^^^^^^
File "/api/langgraph_api/lifespan.py", line 29, in lifespan
File "/usr/local/lib/python3.12/site-packages/langgraph_storage/database.py", line 149, in start_pool
await migrate_vector_index()
File "/usr/local/lib/python3.12/site-packages/langgraph_storage/database.py", line 138, in migrate_vector_index
await lg_store.setup_vector_index(store)
File "/usr/local/lib/python3.12/site-packages/langgraph_storage/store.py", line 94, in setup_vector_index
await cur.execute(sql)
File "/usr/local/lib/python3.12/site-packages/psycopg/cursor_async.py", line 97, in execute
raise ex.with_traceback(None)
psycopg.errors.FeatureNotSupported: extension "vector" is not available
DETAIL: Could not open extension control file "/usr/share/postgresql/16/extension/vector.control": No such file or directory.
HINT: The extension must first be installed on the system where PostgreSQL is running.

error | Application startup failed. Exiting.`

After figuring out how/where to install this pgvector extension in that postgre:16 docker image, the problem was solved.

Hopefully, this will be fixed. It is confusing for someone who's just getting started with LangGraph studio.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant