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 #3332] [BUG]: docker run anythingllm failed on centos7.9 #2144

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

Originally created by @sanpatricky on GitHub (Feb 24, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3332

How are you running AnythingLLM?

Docker (remote machine)

What happened?

docker version:26.1.4

docker run command:
docker run -d
--name anythingllm
-p 3010:3000
-v /data/anythingllm/data:/app/data
-v /data/anythingllm/storage:/app/storage
-v /data/anythingllm/.env:/app/server/.env
--env OLLAMA_ENDPOINT=http://host.docker.internal:11434
mintplexlabs/anythingllm:latest

container log:
node[9]: ../src/node_platform.cc:68:std::unique_ptr node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start(): Assertion (0) == (uv_thread_create(t.get(), start_thread, this))' failed. node[10]: ../src/node_platform.cc:68:std::unique_ptr<long unsigned int> node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start(): Assertion (0) == (uv_thread_create(t.get(), start_thread, this))' failed.
1: 0xb9c1f0 node::Abort() [node]
1: 0xb9c1f0 node::Abort() [node]
2: 0xb9c26e [node]
2: 0xb9c26e [node]
3: 0xc0a39e [node]
3: 0xc0a39e [node]
4: 0xc0a481 node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [node]
4: 0xc0a481 node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [node]
5: 0xb58213 node::InitializeOncePerProcess(std::vector<std::__cxx11::basic_string<char, std::char_traits, std::allocator >, std::allocator<std::__cxx11::basic_string<char, std::char_traits, std::allocator > > > const&, node::ProcessFlags::Flags) [node]
5: 0xb58213 node::InitializeOncePerProcess(std::vector<std::__cxx11::basic_string<char, std::char_traits, std::allocator >, std::allocator<std::__cxx11::basic_string<char, std::char_traits, std::allocator > > > const&, node::ProcessFlags::Flags) [node]
6: 0xb5886b node::Start(int, char**) [node]
6: 0xb5886b node::Start(int, char**) [node]
7: 0x7f83845edd90 [/lib/x86_64-linux-gnu/libc.so.6]
7: 0x7f776a887d90 [/lib/x86_64-linux-gnu/libc.so.6]
8: 0x7f776a887e40 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
8: 0x7f83845ede40 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
9: 0xad779e _start [node]
9: 0xad779e _start [node]
/usr/local/bin/docker-entrypoint.sh: line 8: 10 Aborted (core dumped) node /app/collector/index.js
/usr/local/bin/docker-entrypoint.sh: line 7: 9 Aborted (core dumped) npx prisma generate --schema=./prisma/schema.prisma

Are there known steps to reproduce?

No response

Originally created by @sanpatricky on GitHub (Feb 24, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3332 ### How are you running AnythingLLM? Docker (remote machine) ### What happened? docker version:26.1.4 docker run command: docker run -d \ --name anythingllm \ -p 3010:3000 \ -v /data/anythingllm/data:/app/data \ -v /data/anythingllm/storage:/app/storage \ -v /data/anythingllm/.env:/app/server/.env \ --env OLLAMA_ENDPOINT=http://host.docker.internal:11434 \ mintplexlabs/anythingllm:latest container log: node[9]: ../src/node_platform.cc:68:std::unique_ptr<long unsigned int> node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start(): Assertion `(0) == (uv_thread_create(t.get(), start_thread, this))' failed. node[10]: ../src/node_platform.cc:68:std::unique_ptr<long unsigned int> node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start(): Assertion `(0) == (uv_thread_create(t.get(), start_thread, this))' failed. 1: 0xb9c1f0 node::Abort() [node] 1: 0xb9c1f0 node::Abort() [node] 2: 0xb9c26e [node] 2: 0xb9c26e [node] 3: 0xc0a39e [node] 3: 0xc0a39e [node] 4: 0xc0a481 node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [node] 4: 0xc0a481 node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [node] 5: 0xb58213 node::InitializeOncePerProcess(std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&, node::ProcessFlags::Flags) [node] 5: 0xb58213 node::InitializeOncePerProcess(std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&, node::ProcessFlags::Flags) [node] 6: 0xb5886b node::Start(int, char**) [node] 6: 0xb5886b node::Start(int, char**) [node] 7: 0x7f83845edd90 [/lib/x86_64-linux-gnu/libc.so.6] 7: 0x7f776a887d90 [/lib/x86_64-linux-gnu/libc.so.6] 8: 0x7f776a887e40 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6] 8: 0x7f83845ede40 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6] 9: 0xad779e _start [node] 9: 0xad779e _start [node] /usr/local/bin/docker-entrypoint.sh: line 8: 10 Aborted (core dumped) node /app/collector/index.js /usr/local/bin/docker-entrypoint.sh: line 7: 9 Aborted (core dumped) npx prisma generate --schema=./prisma/schema.prisma ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:28:20 -05:00
yindo closed this issue 2026-02-22 18:28:20 -05:00
yindo commented 2026-02-22 18:28:20 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Feb 25, 2025):

Seems to be an incompatibility with the local DB ORM: https://github.com/prisma/prisma/issues/10649

Without more information on the base OS/CPU it would be hard to know if the binary is compatible or available on your distro.

Additionally, but likely unrelated.
pinned issue: https://github.com/Mintplex-Labs/anything-llm/issues/1331
The CPU instruction set is too old/incompatible

@timothycarambat commented on GitHub (Feb 25, 2025): Seems to be an incompatibility with the local DB ORM: https://github.com/prisma/prisma/issues/10649 Without more information on the base OS/CPU it would be hard to know if the binary is compatible or available on your distro. Additionally, but likely unrelated. pinned issue: https://github.com/Mintplex-Labs/anything-llm/issues/1331 The CPU instruction set is too old/incompatible
yindo commented 2026-02-22 18:28:20 -05:00
Author
Owner
Copy Link
Copy Source

@sanpatricky commented on GitHub (Feb 26, 2025):

Seems to be an incompatibility with the local DB ORM: prisma/prisma#10649

Without more information on the base OS/CPU it would be hard to know if the binary is compatible or available on your distro.

Additionally, but likely unrelated. pinned issue: #1331 The CPU instruction set is too old/incompatible

Thank you, your reply gives correct direction. It is a old node with old CPU. I will try mintplexlabs/anythingllm:lancedb_revert later.

@sanpatricky commented on GitHub (Feb 26, 2025): > Seems to be an incompatibility with the local DB ORM: [prisma/prisma#10649](https://github.com/prisma/prisma/issues/10649) > > Without more information on the base OS/CPU it would be hard to know if the binary is compatible or available on your distro. > > Additionally, but likely unrelated. pinned issue: [#1331](https://github.com/Mintplex-Labs/anything-llm/issues/1331) The CPU instruction set is too old/incompatible Thank you, your reply gives correct direction. It is a old node with old CPU. I will try mintplexlabs/anythingllm:lancedb_revert later.
yindo changed title from [BUG]: docker run anythingllm failed on centos7.9 to [GH-ISSUE #3332] [BUG]: docker run anythingllm failed on centos7.9 2026-06-05 14:44:48 -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#2144
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?