-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Unable to load sqlite-vec extensions in docker environment #1543
Comments
Hello @iankm! Welcome to the ai16z community. Thank you for opening your first issue; we appreciate your contribution. You are now a ai16z contributor! |
Can reproduce the issue, seems this is because the package doesn't have a |
Can you try running: |
Will do |
This worked! Thank you |
This issue should be closed. |
Greetings, stumbled upon the same issue. Tried to run Stacktrace 1 (during first try):
Stacktrace 2 (second try):
Does anyone faced the same? I would appreciate any help on that. |
Are you running DockerHub or Orbstack? Orbstack is better for building docker for platform= linux/amd64 |
DockerHub. I've resolved the issue by following zxflows' answer in "ElizaOS Development" Discord channel. To fix it, in Docker Desktop general settings I've changed Virtual Machine option to "Docker VMM" instead of "Apple Virtualization Framework" and built the image. Many thanks Discord message link: https://discord.com/channels/1051457140637827122/1323727516745334785/1325014844075937792 |
Closing this issue because not related to the general avaiable code. |
Describe the bug
Upon building the docker container and running locally, I am unable to start my agent. The agent works when I build in my local terminal.
When I run the docker container, I receive the issue in the provided screenshot.
I mainly interact with my agent via the Discord client. When I run locally, it responds to my messages and I can see the logs in terminal. When I run via docker, this does not occur.
To Reproduce
docker build -t latest .
docker run latest
Expected behavior
I should be able to interact with my agent via Discord and see the appropriate logs in my terminal.
Screenshots
Additional context
The text was updated successfully, but these errors were encountered: