Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #1996] [BUG]: docker cannot run #1299

New Issue
Closed
opened 2026-02-22 18:24:09 -05:00 by yindo · 2 comments
yindo commented 2026-02-22 18:24:09 -05:00
Owner
Copy Link
Copy Source

Originally created by @yangg on GitHub (Jul 29, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1996

How are you running AnythingLLM?

Docker (local)

What happened?

export STORAGE_LOCATION=$HOME/anythingllm && \
mkdir -p $STORAGE_LOCATION && \
touch "$STORAGE_LOCATION/.env" && \
docker run -d -p 3001:3001 \
  --name any \
  --cap-add SYS_ADMIN \
  -v ${STORAGE_LOCATION}:/app/server/storage \
  -v ${STORAGE_LOCATION}/.env:/app/server/.env \
  -e STORAGE_DIR="/app/server/storage" \
  mintplexlabs/anythingllm

c6d3b5020cbcc649f30405e3b8b41c222024e495d02e862a089ce2b1ffd32faf
docker logs -f any
[collector] info: Collector hot directory and tmp storage wiped!
[collector] info: Document processor app listening on port 8888
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma

✔ Generated Prisma Client (v5.3.1) to ./node_modules/@prisma/client in 755ms

Start using Prisma Client in Node.js (See: https://pris.ly/d/client)

import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()

or start using Prisma Client at the edge (See: https://pris.ly/d/accelerate)

import { PrismaClient } from '@prisma/client/edge'
const prisma = new PrismaClient()


See other ways of importing Prisma Client: http://pris.ly/d/importing-client

Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "anythingllm.db" at "file:../storage/anythingllm.db"

Error: Schema engine error:
SQLite database error
unable to open database file: ../storage/anythingllm.db

the database url in schema.prisma seems error

Are there known steps to reproduce?

following the docker install doc.

Originally created by @yangg on GitHub (Jul 29, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1996 ### How are you running AnythingLLM? Docker (local) ### What happened? ``` export STORAGE_LOCATION=$HOME/anythingllm && \ mkdir -p $STORAGE_LOCATION && \ touch "$STORAGE_LOCATION/.env" && \ docker run -d -p 3001:3001 \ --name any \ --cap-add SYS_ADMIN \ -v ${STORAGE_LOCATION}:/app/server/storage \ -v ${STORAGE_LOCATION}/.env:/app/server/.env \ -e STORAGE_DIR="/app/server/storage" \ mintplexlabs/anythingllm c6d3b5020cbcc649f30405e3b8b41c222024e495d02e862a089ce2b1ffd32faf docker logs -f any [collector] info: Collector hot directory and tmp storage wiped! [collector] info: Document processor app listening on port 8888 Environment variables loaded from .env Prisma schema loaded from prisma/schema.prisma ✔ Generated Prisma Client (v5.3.1) to ./node_modules/@prisma/client in 755ms Start using Prisma Client in Node.js (See: https://pris.ly/d/client) import { PrismaClient } from '@prisma/client' const prisma = new PrismaClient() or start using Prisma Client at the edge (See: https://pris.ly/d/accelerate) import { PrismaClient } from '@prisma/client/edge' const prisma = new PrismaClient() See other ways of importing Prisma Client: http://pris.ly/d/importing-client Environment variables loaded from .env Prisma schema loaded from prisma/schema.prisma Datasource "db": SQLite database "anythingllm.db" at "file:../storage/anythingllm.db" Error: Schema engine error: SQLite database error unable to open database file: ../storage/anythingllm.db ``` the database url in schema.prisma seems error ### Are there known steps to reproduce? following the docker install doc.
yindo added the possible bug label 2026-02-22 18:24:09 -05:00
yindo closed this issue 2026-02-22 18:24:09 -05:00
yindo commented 2026-02-22 18:24:10 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jul 30, 2024):

There is no error - the docker user probably could not write a file to the $HOME/anythingllm folder due to permissions. I would first check there and also try to chmod -R 777 $HOME/anythingllm to be sure the folder is writeable by the docker user. If that also fails you may need to manually create $HOME/anythingllm/anythingllm.db

@timothycarambat commented on GitHub (Jul 30, 2024): There is no error - the docker user probably could not write a file to the `$HOME/anythingllm` folder due to permissions. I would first check there and also try to `chmod -R 777 $HOME/anythingllm` to be sure the folder is writeable by the docker user. If that also fails you may need to manually create `$HOME/anythingllm/anythingllm.db`
yindo commented 2026-02-22 18:24:10 -05:00
Author
Owner
Copy Link
Copy Source

@yangg commented on GitHub (Jul 30, 2024):

My bad, I thought the issue was with the path, but I didn't realize the error message 'unable to open database file' was indicating a permission problem.

@yangg commented on GitHub (Jul 30, 2024): My bad, I thought the issue was with the path, but I didn't realize the error message 'unable to open database file' was indicating a permission problem.
yindo changed title from [BUG]: docker cannot run to [GH-ISSUE #1996] [BUG]: docker cannot run 2026-06-05 14:40:00 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#1299
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?