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 #4522] [BUG]: Docker init choose llm provider cause the docker to crash #2876

New Issue
Closed
opened 2026-02-22 18:31:37 -05:00 by yindo · 1 comment
yindo commented 2026-02-22 18:31:37 -05:00
Owner
Copy Link
Copy Source

Originally created by @flychmove on GitHub (Oct 10, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4522

How are you running AnythingLLM?

Docker (local)

What happened?

I'm using docker deployment, after going to the page and selecting the llm provider, after entering the information and clicking the next button it reports an error:"Failed to save LLM settings: Failed to fetch". And I've found that this is when the docker container crashes.
Here is the logs:
[collector] info: [TikTokenTokenizer] Initialized new TikTokenTokenizer instance.
[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 495ms

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"
SQLite database anythingllm.db created at file:../storage/anythingllm.db
33 migrations found in prisma/migrations
Applying migration 20230921191814_init
Applying migration 20231101001441_init
...

All migrations have been successfully applied.

┌─────────────────────────────────────────────────────────┐
│ Update available 5.3.1 -> 6.17.0 │
│ │
│ This is a major update - please follow the guide at │
│ https://pris.ly/d/major-version-upgrade │
│ │
│ Run the following to update │
│ npm i --save-dev prisma@latest │
│ npm i @prisma/client@latest │
└─────────────────────────────────────────────────────────┘

[backend] info: [EncryptionManager] Self-assigning key & salt for encrypting arbitrary data.
[backend] info: [TokenManager] Initialized new TokenManager instance for model: gpt-3.5-turbo
[backend] info: [ContextWindowFinder] Pulling remote model map...
[backend] info: [TokenManager] Returning existing instance for model: gpt-3.5-turbo
[backend] info: [TELEMETRY ENABLED] Anonymous Telemetry enabled. Telemetry helps Mintplex Labs Inc improve AnythingLLM.
[backend] info: prisma:info Starting a sqlite pool with 53 connections.
[backend] info: [TELEMETRY SENT] {"event":"server_boot","distinctId":"b754874b-4176-464f-aa56-963244307443","properties":{"commit":"--","runtime":"docker"}}
[backend] info: [CommunicationKey] RSA key pair generated for signed payloads within AnythingLLM services.
[backend] info: [EncryptionManager] Loaded existing key & salt for encrypting arbitrary data.
[backend] info: Primary server in HTTP mode listening on port 3001
[backend] info: [BackgroundWorkerService] Starting...
[backend] info: [BackgroundWorkerService] Service started with 1 jobs ["cleanup-orphan-documents"]

[backend] info: [ContextWindowFinder] Error syncing remote model map TypeError: fetch failed

 at node:internal/deps/undici/undici:12637:11

 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

 at async #pullRemoteModelMap (/app/server/utils/AiProviders/modelMap/index.js:99:37)

prisma:info Starting a sqlite pool with 53 connections.

[backend] info: [206:249]: No direct uploads path found - exiting.

[bg-worker][cleanup-orphan-documents] info: [206:249]: No direct uploads path found - exiting.

[backend] warn: Child process exited with code 0 and signal null

[backend] info: Worker for job "cleanup-orphan-documents" exited with code 0

[backend] info: EmbeddingEngine changed from undefined to native - resetting undefined namespaces

[backend] info: [Event Logged] - workspace_vectors_reset

[backend] info: Resetting anythingllm managed vector namespaces for

/usr/local/bin/docker-entrypoint.sh: line 24: 206 Illegal instruction (core dumped) node /app/server/index.js

Are there known steps to reproduce?

Use docker to run the latest image, page initialization select llm provider(use generic open ai) and click next appears

Originally created by @flychmove on GitHub (Oct 10, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4522 ### How are you running AnythingLLM? Docker (local) ### What happened? I'm using docker deployment, after going to the page and selecting the llm provider, after entering the information and clicking the next button it reports an error:"Failed to save LLM settings: Failed to fetch". And I've found that this is when the docker container crashes. Here is the logs: [collector] info: [TikTokenTokenizer] Initialized new TikTokenTokenizer instance. [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 495ms 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" SQLite database anythingllm.db created at file:../storage/anythingllm.db 33 migrations found in prisma/migrations Applying migration `20230921191814_init` Applying migration `20231101001441_init` ... All migrations have been successfully applied. ┌─────────────────────────────────────────────────────────┐ │ Update available 5.3.1 -> 6.17.0 │ │ │ │ This is a major update - please follow the guide at │ │ https://pris.ly/d/major-version-upgrade │ │ │ │ Run the following to update │ │ npm i --save-dev prisma@latest │ │ npm i @prisma/client@latest │ └─────────────────────────────────────────────────────────┘ [backend] info: [EncryptionManager] Self-assigning key & salt for encrypting arbitrary data. [backend] info: [TokenManager] Initialized new TokenManager instance for model: gpt-3.5-turbo [backend] info: [ContextWindowFinder] Pulling remote model map... [backend] info: [TokenManager] Returning existing instance for model: gpt-3.5-turbo [backend] info: [TELEMETRY ENABLED] Anonymous Telemetry enabled. Telemetry helps Mintplex Labs Inc improve AnythingLLM. [backend] info: prisma:info Starting a sqlite pool with 53 connections. [backend] info: [TELEMETRY SENT] {"event":"server_boot","distinctId":"b754874b-4176-464f-aa56-963244307443","properties":{"commit":"--","runtime":"docker"}} [backend] info: [CommunicationKey] RSA key pair generated for signed payloads within AnythingLLM services. [backend] info: [EncryptionManager] Loaded existing key & salt for encrypting arbitrary data. [backend] info: Primary server in HTTP mode listening on port 3001 [backend] info: [BackgroundWorkerService] Starting... [backend] info: [BackgroundWorkerService] Service started with 1 jobs ["cleanup-orphan-documents"] [backend] info: [ContextWindowFinder] Error syncing remote model map TypeError: fetch failed at node:internal/deps/undici/undici:12637:11 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async #pullRemoteModelMap (/app/server/utils/AiProviders/modelMap/index.js:99:37) prisma:info Starting a sqlite pool with 53 connections. [backend] info: [206:249]: No direct uploads path found - exiting. [bg-worker][cleanup-orphan-documents] info: [206:249]: No direct uploads path found - exiting. [backend] warn: Child process exited with code 0 and signal null [backend] info: Worker for job "cleanup-orphan-documents" exited with code 0 [backend] info: EmbeddingEngine changed from undefined to native - resetting undefined namespaces [backend] info: [Event Logged] - workspace_vectors_reset [backend] info: Resetting anythingllm managed vector namespaces for /usr/local/bin/docker-entrypoint.sh: line 24: 206 Illegal instruction (core dumped) node /app/server/index.js ### Are there known steps to reproduce? Use docker to run the latest image, page initialization select llm provider(use generic open ai) and click next appears
yindo added the possible bug label 2026-02-22 18:31:37 -05:00
yindo closed this issue 2026-02-22 18:31:37 -05:00
yindo commented 2026-02-22 18:31:37 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Oct 10, 2025):

/usr/local/bin/docker-entrypoint.sh: line 24: 206 Illegal instruction (core dumped) node /app/server/index.js

You are on a machine without AVX2 support, which is required by lancedb the default vector DB. This is a pinned issue with the exact same message you got

Open the Storage folder .env and set VECTOR_DB to some other vector DB provider with its config and it will work

@timothycarambat commented on GitHub (Oct 10, 2025): > /usr/local/bin/docker-entrypoint.sh: line 24: 206 Illegal instruction (core dumped) node /app/server/index.js You are on a machine without AVX2 support, which is required by `lancedb` the default vector DB. [This is a pinned issue with the exact same message you got](https://github.com/Mintplex-Labs/anything-llm/issues/1331) Open the Storage folder `.env` and set `VECTOR_DB` to some other vector DB provider with its config and it will work
yindo changed title from [BUG]: Docker init choose llm provider cause the docker to crash to [GH-ISSUE #4522] [BUG]: Docker init choose llm provider cause the docker to crash 2026-06-05 14:49:01 -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#2876
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?