-
Notifications
You must be signed in to change notification settings - Fork 114
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
AnythingLLM client image crashes on Mac #91
Comments
Tested on MacBookPro M3 14.6.1, podman 5.2.1 |
If the image starts, you have access to AnythingLLM, and are able to configure the endpoint, I would say that the issue is not with the image or the launcher itself. The log refers to it because the main process is launched from there, but what seems to trigger is above. |
I have re-tried using the appropriate model, and disabling the local firewall (LittleSnitch) just in case. I could reproduce the issue:
Digging a bit deeper in the logs I see these worrying lines:
I set the API key as provided by the MaaS platform. |
This part is normal the first time you launch AnythingLLM, when the Endpoint is not yet configured. By default it thinks you will use OpenAI, and tries to find the key in the environment variables. Once you have everything configured (and persisted) it does not show anymore. The real error is this one:
However, apart from the core dump, it does not say much... And from a quick search, it seems that this type of error happens on different flavours of Macs running containers. It always ends up with the illegal instruction/code dump as it's what launches the process, but the error is in the app itself. |
Oh, yes, I'm so dumb! It's a standard image, made to work primarily on OpenShift. So definitely not made for Apple Silicon. |
"I have tried to run it locally with an M-Series mac but the image is crashing as soon as I perform a request.
Tested against a ollama model served locally as well as a granite model served on MaaS"
"the image is running and I could configure it ok with the endpoint and the API key"
The text was updated successfully, but these errors were encountered: