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

[GH-ISSUE #2294] [BUG]: docker image crashes #1499

New Issue
Closed
opened 2026-02-22 18:25:08 -05:00 by yindo · 3 comments
yindo commented 2026-02-22 18:25:08 -05:00
Owner
Copy Link
Copy Source

Originally created by @thistleknot on GitHub (Sep 15, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2294

How are you running AnythingLLM?

Docker (local)

What happened?

docker pull mintplexlabs/anythingllm

export STORAGE_LOCATION=/mnt/intRaid_/anythingllm

touch "$STORAGE_LOCATION/.env"

ls /mnt/intRaid_/anythingllm/ -latr

docker run -d -p 3001:3001 --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

crashes

docker logs a7a0dff32a25023fcd7b3ce57f976f643ca067e850563096fde9eca740b0e726

[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 1.17s

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

Are there known steps to reproduce?

Steps to Reproduce the Error

docker pull mintplexlabs/anythingllm

export STORAGE_LOCATION=/mnt/intRaid_/anythingllm

ls /mnt/intRaid_/anythingllm

touch "$STORAGE_LOCATION/.env"

docker run -d -p 3001:3001 --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

docker logs <container_id>

python 3.10
oracle linux 8

Originally created by @thistleknot on GitHub (Sep 15, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2294 ### How are you running AnythingLLM? Docker (local) ### What happened? ``` docker pull mintplexlabs/anythingllm export STORAGE_LOCATION=/mnt/intRaid_/anythingllm touch "$STORAGE_LOCATION/.env" ls /mnt/intRaid_/anythingllm/ -latr docker run -d -p 3001:3001 --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 ``` crashes ``` docker logs a7a0dff32a25023fcd7b3ce57f976f643ca067e850563096fde9eca740b0e726 ``` [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 1.17s 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 ### Are there known steps to reproduce? Steps to Reproduce the Error ``` docker pull mintplexlabs/anythingllm export STORAGE_LOCATION=/mnt/intRaid_/anythingllm ls /mnt/intRaid_/anythingllm touch "$STORAGE_LOCATION/.env" docker run -d -p 3001:3001 --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 docker logs <container_id> ``` python 3.10 oracle linux 8
yindo added the possible bug label 2026-02-22 18:25:08 -05:00
yindo closed this issue 2026-02-22 18:25:08 -05:00
yindo commented 2026-02-22 18:25:08 -05:00
Author
Owner
Copy Link
Copy Source

@thistleknot commented on GitHub (Sep 15, 2024):

fixed
chmod -R 777 /mnt/{whereve you are mounting using -v}
https://github.com/Mintplex-Labs/anything-llm/issues/1996

@thistleknot commented on GitHub (Sep 15, 2024): fixed chmod -R 777 /mnt/{whereve you are mounting using -v} https://github.com/Mintplex-Labs/anything-llm/issues/1996
yindo commented 2026-02-22 18:25:08 -05:00
Author
Owner
Copy Link
Copy Source

@ShivamB25 commented on GitHub (May 23, 2025):

fixed chmod -R 777 /mnt/{whereve you are mounting using -v} #1996

it is a very known bug. maybe can u put it on docs ?

@ShivamB25 commented on GitHub (May 23, 2025): > fixed chmod -R 777 /mnt/{whereve you are mounting using -v} [#1996](https://github.com/Mintplex-Labs/anything-llm/issues/1996) it is a very known bug. maybe can u put it on docs ?
yindo commented 2026-02-22 18:25:08 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 24, 2025):

It's not a bug, it's just how linux works when you try mounting a userland application to a generic top-level folder 🤷

I guess its worth putting in docs for those that dont know since it seems to happen a lot!

@timothycarambat commented on GitHub (May 24, 2025): It's not a bug, it's just how linux works when you try mounting a userland application to a generic top-level folder 🤷 I guess its worth putting in docs for those that dont know since it seems to happen a lot!
yindo changed title from [BUG]: docker image crashes to [GH-ISSUE #2294] [BUG]: docker image crashes 2026-06-05 14:41:05 -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#1499
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?