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 #3481] [BUG]: docker AnythingLLM auto stop #2249

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

Originally created by @Kapsugar on GitHub (Mar 17, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3481

How are you running AnythingLLM?

Docker (remote machine)

What happened?

When I deployed AnythingLLM using Docker, after selecting the model and clicking "Next" on the interface, it threw this error. I've also included the backend logs below. I'm using an x86 environment, and both the image and Docker are x86-based. How can I resolve this?

Image

this is error log

All migrations have been successfully applied.
┌─────────────────────────────────────────────────────────┐
│ Update available 5.3.1 -> 6.5.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: [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 7 connections.
[backend] info: [TELEMETRY SENT] {"event":"server_boot","distinctId":"884daea3-3643-4fee-8520-386a677904ac","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] Feature is not enabled and will not be started.
[backend] info: [MetaGenerator] fetching custom meta tag settings...
[backend] error: Error: The OPENAI_API_KEY environment variable is missing or empty; either provide it, or instantiate the OpenAI client with an apiKey option, like new OpenAI({ apiKey: 'My API Key' }).
at new OpenAI (/app/server/node_modules/openai/index.js:53:19)
at openAiModels (/app/server/utils/helpers/customModels.js:91:18)
at getCustomModels (/app/server/utils/helpers/customModels.js:43:20)
at /app/server/endpoints/system.js:960:41
at Layer.handle [as handle_request] (/app/server/node_modules/express/lib/router/layer.js:95:5)
at next (/app/server/node_modules/express/lib/router/route.js:149:13)
at /app/server/utils/middleware/multiUserProtected.js:60:7
at Layer.handle [as handle_request] (/app/server/node_modules/express/lib/router/layer.js:95:5)
at next (/app/server/node_modules/express/lib/router/route.js:149:13)
at validatedRequest (/app/server/utils/middleware/validatedRequest.js:20:5)
[backend] error: TypeError: fetch failed
at node:internal/deps/undici/undici:12625:11
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async ollamaAIModels (/app/server/utils/helpers/customModels.js:346:18)
at async getCustomModels (/app/server/utils/helpers/customModels.js:49:14)
at async /app/server/endpoints/system.js:960:35
[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 7: 113 Illegal instruction (core dumped) node /app/server/index.js

Are there known steps to reproduce?

No response

Originally created by @Kapsugar on GitHub (Mar 17, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3481 ### How are you running AnythingLLM? Docker (remote machine) ### What happened? When I deployed AnythingLLM using Docker, after selecting the model and clicking "Next" on the interface, it threw this error. I've also included the backend logs below. I'm using an x86 environment, and both the image and Docker are x86-based. How can I resolve this? ![Image](https://github.com/user-attachments/assets/f50e6b49-39e7-4b14-8f7f-9402978cf888) this is error log All migrations have been successfully applied. ┌─────────────────────────────────────────────────────────┐ │ Update available 5.3.1 -> 6.5.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: [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 7 connections. [backend] info: [TELEMETRY SENT] {"event":"server_boot","distinctId":"884daea3-3643-4fee-8520-386a677904ac","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] Feature is not enabled and will not be started. [backend] info: [MetaGenerator] fetching custom meta tag settings... [backend] error: Error: The OPENAI_API_KEY environment variable is missing or empty; either provide it, or instantiate the OpenAI client with an apiKey option, like new OpenAI({ apiKey: 'My API Key' }). at new OpenAI (/app/server/node_modules/openai/index.js:53:19) at openAiModels (/app/server/utils/helpers/customModels.js:91:18) at getCustomModels (/app/server/utils/helpers/customModels.js:43:20) at /app/server/endpoints/system.js:960:41 at Layer.handle [as handle_request] (/app/server/node_modules/express/lib/router/layer.js:95:5) at next (/app/server/node_modules/express/lib/router/route.js:149:13) at /app/server/utils/middleware/multiUserProtected.js:60:7 at Layer.handle [as handle_request] (/app/server/node_modules/express/lib/router/layer.js:95:5) at next (/app/server/node_modules/express/lib/router/route.js:149:13) at validatedRequest (/app/server/utils/middleware/validatedRequest.js:20:5) [backend] error: TypeError: fetch failed at node:internal/deps/undici/undici:12625:11 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async ollamaAIModels (/app/server/utils/helpers/customModels.js:346:18) at async getCustomModels (/app/server/utils/helpers/customModels.js:49:14) at async /app/server/endpoints/system.js:960:35 [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 7: 113 Illegal instruction (core dumped) node /app/server/index.js ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:28:50 -05:00
yindo closed this issue 2026-02-22 18:28:50 -05:00
yindo commented 2026-02-22 18:28:50 -05:00
Author
Owner
Copy Link
Copy Source

@Kapsugar commented on GitHub (Mar 17, 2025):

The Ollama configuration is all normal, and I can successfully call this large model using the desktop version of AnythingLLM. Below is my container creation command.

docker run -d -p 3001:3001
--name anythingllm
--cap-add SYS_ADMIN
--add-host=host.docker.internal:host-gateway
-v ${STORAGE_LOCATION}:/app/server/storage
-v ${STORAGE_LOCATION}/.env:/app/server/.env
-e STORAGE_DIR="/app/server/storage"
mintplexlabs/anythingllm

@Kapsugar commented on GitHub (Mar 17, 2025): The Ollama configuration is all normal, and I can successfully call this large model using the desktop version of AnythingLLM. Below is my container creation command. docker run -d -p 3001:3001 \ --name anythingllm \ --cap-add SYS_ADMIN \ --add-host=host.docker.internal:host-gateway \ -v ${STORAGE_LOCATION}:/app/server/storage \ -v ${STORAGE_LOCATION}/.env:/app/server/.env \ -e STORAGE_DIR="/app/server/storage" \ mintplexlabs/anythingllm
yindo commented 2026-02-22 18:28:50 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Mar 17, 2025):

This happens when you cannot write to STORAGE_LOCATION or if you search GH for issues related to
/usr/local/bin/docker-entrypoint.sh: line 7: 113 Illegal instruction (core dumped) node /app/server/index.js

You will find this often occurs when your underlying CPU cannot run the prisma binary and aborts. This works on desktop because the prisma client is slightly different in how it detects the runtime to use, whereas in the docker container it will always try to run the Linux runtime that is incompatible with the CPU (requires AVX2)

@timothycarambat commented on GitHub (Mar 17, 2025): This happens when you cannot write to `STORAGE_LOCATION` or if you search GH for issues related to `/usr/local/bin/docker-entrypoint.sh: line 7: 113 Illegal instruction (core dumped) node /app/server/index.js` You will find this often occurs when your underlying CPU cannot run the prisma binary and aborts. This works on desktop because the prisma client is slightly different in how it detects the runtime to use, whereas in the docker container it will always try to run the Linux runtime that is incompatible with the CPU (requires AVX2)
yindo changed title from [BUG]: docker AnythingLLM auto stop to [GH-ISSUE #3481] [BUG]: docker AnythingLLM auto stop 2026-06-05 14:45:25 -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#2249
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?