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 #3690] [BUG]: "Illegal instruction (core dumped)" Error on Intel Celeron N5105 CPU #2380

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

Originally created by @Curiosa-07 on GitHub (Apr 21, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3690

How are you running AnythingLLM?

Docker (local)

What happened?

Issue: "Illegal instruction (core dumped)" Error on Intel Celeron N5105 CPU

This is my first time creating an issue on GitHub, so I'm using AI assistance to help with the writing. Thank you for your understanding.

System Information

  • CPU: Intel Celeron N5105 @ 2.00GHz (Jasper Lake)
  • Architecture: x86_64
  • OS: Linux
  • Docker Image: mintplexlabs/anythingllm (latest)
  • Node.js Version: v18.20.8
  • npm Version: 10.8.2
  • yarn Version: 1.22.22

Issue Description

I'm experiencing an "Illegal instruction (core dumped)" error when running AnythingLLM in a Docker container on my system with an Intel Celeron N5105 processor. The container starts successfully but crashes with this error when executing Node.js.

Docker Command Used

export STORAGE_LOCATION=$HOME/anythingllm && \
mkdir -p $STORAGE_LOCATION && \
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

Additional Setup Steps

I also set full permissions on the AnythingLLM directory to ensure there were no permission issues:

chmod -R 777 $HOME/anythingllm

Error Log

[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 482ms

[...]

[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] 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:   107 Illegal instruction     (core dumped) node /app/server/index.js

What I've Tried

  1. Running with different Docker options
  2. Restarting the container multiple times
  3. Setting full permissions (777) on the storage directory

Additional CPU Information

Architecture:             x86_64
CPU op-mode(s):          32-bit, 64-bit
Address sizes:           39 bits physical, 48 bits virtual
Byte Order:              Little Endian
CPU(s):                  4
Vendor ID:               GenuineIntel
Model name:              Intel(R) Celeron(R) N5105 @ 2.00GHz
CPU family:              6
Model:                   156
Thread(s) per core:      1
Core(s) per socket:      4
Socket(s):               1
CPU max MHz:             2900.0000
CPU min MHz:             800.0000

Question

I believe this is a CPU compatibility issue where the Node.js application or one of its dependencies is trying to use CPU instructions not supported by my Celeron N5105 processor.

Are there any recommended solutions for this issue? Perhaps:

  1. An alternative Docker image tag that's compatible with older CPUs?
  2. Configuration options to disable certain CPU features?
  3. A recommended older version that might be more compatible?

Any assistance would be greatly appreciated. Thank you!

Are there known steps to reproduce?

No response

Originally created by @Curiosa-07 on GitHub (Apr 21, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3690 ### How are you running AnythingLLM? Docker (local) ### What happened? # Issue: "Illegal instruction (core dumped)" Error on Intel Celeron N5105 CPU This is my first time creating an issue on GitHub, so I'm using AI assistance to help with the writing. Thank you for your understanding. ## System Information - **CPU**: Intel Celeron N5105 @ 2.00GHz (Jasper Lake) - **Architecture**: x86_64 - **OS**: Linux - **Docker Image**: mintplexlabs/anythingllm (latest) - **Node.js Version**: v18.20.8 - **npm Version**: 10.8.2 - **yarn Version**: 1.22.22 ## Issue Description I'm experiencing an "Illegal instruction (core dumped)" error when running AnythingLLM in a Docker container on my system with an Intel Celeron N5105 processor. The container starts successfully but crashes with this error when executing Node.js. ## Docker Command Used ```bash export STORAGE_LOCATION=$HOME/anythingllm && \ mkdir -p $STORAGE_LOCATION && \ 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 ``` ## Additional Setup Steps I also set full permissions on the AnythingLLM directory to ensure there were no permission issues: ```bash chmod -R 777 $HOME/anythingllm ``` ## Error Log ``` [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 482ms [...] [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] 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: 107 Illegal instruction (core dumped) node /app/server/index.js ``` ## What I've Tried 1. Running with different Docker options 2. Restarting the container multiple times 3. Setting full permissions (777) on the storage directory ## Additional CPU Information ``` Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 39 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 4 Vendor ID: GenuineIntel Model name: Intel(R) Celeron(R) N5105 @ 2.00GHz CPU family: 6 Model: 156 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 CPU max MHz: 2900.0000 CPU min MHz: 800.0000 ``` ## Question I believe this is a CPU compatibility issue where the Node.js application or one of its dependencies is trying to use CPU instructions not supported by my Celeron N5105 processor. Are there any recommended solutions for this issue? Perhaps: 1. An alternative Docker image tag that's compatible with older CPUs? 2. Configuration options to disable certain CPU features? 3. A recommended older version that might be more compatible? Any assistance would be greatly appreciated. Thank you! ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:29:25 -05:00
yindo closed this issue 2026-02-22 18:29:25 -05:00
yindo commented 2026-02-22 18:29:26 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Apr 21, 2025):

I believe this is a CPU compatibility issue where the Node.js application or one of its dependencies is trying to use CPU instructions not supported by my Celeron N5105 processor.

Correct, as you can see by viewing just searching the issue in our existing issues - it is also a pinned issue at the top - which also has a comment that mentions a Docker tag that supports older CPUs.

We do not actively maintain this tag because it is so old and out of date.

That being said, if you also change the vector DB in use to anything else besides the default, you will get around this issue.

CPU does not support AVX2, which is required for the default lanceDB vector db.
https://www.intel.com/content/www/us/en/products/sku/212328/intel-celeron-processor-n5105-4m-cache-up-to-2-90-ghz/specifications.html

@timothycarambat commented on GitHub (Apr 21, 2025): > I believe this is a CPU compatibility issue where the Node.js application or one of its dependencies is trying to use CPU instructions not supported by my Celeron N5105 processor. Correct, as you can see by viewing just searching the [issue in our existing issues](https://github.com/Mintplex-Labs/anything-llm/issues?q=is%3Aissue%20state%3Aclosed%20illegal%20instruction) - it is also a [pinned issue at the top](https://github.com/Mintplex-Labs/anything-llm/issues/1331) - which also has a comment that mentions a [Docker tag](https://github.com/Mintplex-Labs/anything-llm/issues/1331#issuecomment-2661527806) that supports older CPUs. We _do not actively maintain_ this tag because it is so old and out of date. That being said, if you also change the vector DB in use to anything else besides the default, you will get around this issue. CPU does not support AVX2, which is required for the default lanceDB vector db. https://www.intel.com/content/www/us/en/products/sku/212328/intel-celeron-processor-n5105-4m-cache-up-to-2-90-ghz/specifications.html
yindo changed title from [BUG]: "Illegal instruction (core dumped)" Error on Intel Celeron N5105 CPU to [GH-ISSUE #3690] [BUG]: "Illegal instruction (core dumped)" Error on Intel Celeron N5105 CPU 2026-06-05 14:46:14 -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#2380
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?