search

av / harbor

Effortlessly run LLM backends, APIs, frontends, and services with one command.
https://github.com/av/harbor
Apache License 2.0
1.6k stars 107 forks source link

AnythingLLM Exited (1) Error & Solution #100

Closed Lensman89 closed 3 months ago

Lensman89 commented 3 months ago

Hi, I would like to inform about any issue present regarding AnythingLLM. On a clean installation of harbor when installing and trying to run AnythingLLM I'm presented with the message:

container harbor.anythingllm exited (1)

Running harbor logs anythingllm

I'm provided with this logs:

harbor.anythingllm | harbor.anythingllm | import { PrismaClient } from '@prisma/client' harbor.anythingllm | const prisma = new PrismaClient() harbor.anythingllm | harbor.anythingllm | or start using Prisma Client at the edge (See: https://pris.ly/d/accelerate) harbor.anythingllm | harbor.anythingllm | import { PrismaClient } from '@prisma/client/edge' harbor.anythingllm | const prisma = new PrismaClient() harbor.anythingllm | harbor.anythingllm | harbor.anythingllm | See other ways of importing Prisma Client: http://pris.ly/d/importing-client harbor.anythingllm | harbor.anythingllm | Environment variables loaded from .env harbor.anythingllm | Prisma schema loaded from prisma/schema.prisma harbor.anythingllm | Datasource "db": SQLite database "anythingllm.db" at "file:../storage/anythingllm.db" harbor.anythingllm | harbor.anythingllm | Error: Schema engine error: harbor.anythingllm | SQLite database error harbor.anythingllm | unable to open database file: ../storage/anythingllm.db harbor.anythingllm |

But after searching around and checking around the documentation of AnythingLLM's website i found that usually this is cause by a permission issue that anythingllm is not able to access the storage location. So the possible two solutions are: or change the location of the storage to a location that it doesn't require root permission or chmod the current location.

To test it i run: sudo chown -R 1000:1000 /home/vllm/.harbor/anythingllm Note: vllm is just the name of my user as i'm running on LXC to play with harbor.

And after that I was able to run and access anythingllm succesfully.

The solution I found from another github link: https://github.com/Mintplex-Labs/anything-llm/issues/2077

In case someone faces the same issue as me.

Regards !

av commented 3 months ago

Hi, thanks for trying out Harbor!

Indeed, there are also many other services that require specific file access permissions on the volumes mounted from the host. Unfortunately, sometimes services are also not self-consistent, or the permissions are changed on the host due to some automated process.

Harbor comes with a utility (works only on Linux) to help with such situations.

The downside is that this operation is potentially unsafe: it enables access to the files from other containers that might happen to have the same GID/UIDs. Because of this and the Linux being only supported platfrom it's not documented as an official solution.

harbor fixfs

It'll ensure to apply FS ACLs for all locations managed by Harbor so that they are available both to the host user and the users from the containers.

To help with the problem, I've added following new docs to the wiki:

That said - I'm curious about any other way to solve it in a more general way, but I haven't been able to find anything that'd be applicable to Harbor at the time of writing.