[GH-ISSUE #2120] [BUG]: Meet some error when i start up a docker image #1382

Closed
opened 2026-02-22 18:24:32 -05:00 by yindo · 4 comments
Owner

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

How are you running AnythingLLM?

Docker (local)

What happened?

System: CentOS 7.7.1908

Docker repository: mintplexlabs/anythingllm

Start up command:

(llm) [root@gpu llm]#  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
5019cc24e9f4acf4ee1f03a305a20cb8705da71cfaf648c828ba253f735dcb71

I just copy from here: https://docs.anythingllm.com/installation/desktop/linux#install-using-the-installer-script

Log:

(base) [root@gpu llm]# docker logs ef3772dd98dd
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[8]: ../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: 0xc0a17e  [node]
 3: 0xc0a17e  [node]
 4: 0xc0a261 node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [node]
 4: 0xc0a261 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: 0x7fa6c9f6ed90  [/lib/x86_64-linux-gnu/libc.so.6]
 7: 0x7fbef2265d90  [/lib/x86_64-linux-gnu/libc.so.6]
 8: 0x7fa6c9f6ee40 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
 8: 0x7fbef2265e40 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
 9: 0xad789e _start [node]
 9: 0xad789e _start [node]
/usr/local/bin/docker-entrypoint.sh: line 7:     8 Aborted                 npx prisma generate --schema=./prisma/schema.prisma
/usr/local/bin/docker-entrypoint.sh: line 8:     9 Aborted                 node /app/collector/index.js

Problem: container start up failed immediatly.

Are there known steps to reproduce?

No response

Originally created by @tigflanker on GitHub (Aug 15, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2120 ### How are you running AnythingLLM? Docker (local) ### What happened? System: CentOS 7.7.1908 Docker repository: mintplexlabs/anythingllm Start up command: ``` (llm) [root@gpu llm]# 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 5019cc24e9f4acf4ee1f03a305a20cb8705da71cfaf648c828ba253f735dcb71 ``` I just copy from here: https://docs.anythingllm.com/installation/desktop/linux#install-using-the-installer-script Log: ``` (base) [root@gpu llm]# docker logs ef3772dd98dd 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[8]: ../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: 0xc0a17e [node] 3: 0xc0a17e [node] 4: 0xc0a261 node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [node] 4: 0xc0a261 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: 0x7fa6c9f6ed90 [/lib/x86_64-linux-gnu/libc.so.6] 7: 0x7fbef2265d90 [/lib/x86_64-linux-gnu/libc.so.6] 8: 0x7fa6c9f6ee40 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6] 8: 0x7fbef2265e40 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6] 9: 0xad789e _start [node] 9: 0xad789e _start [node] /usr/local/bin/docker-entrypoint.sh: line 7: 8 Aborted npx prisma generate --schema=./prisma/schema.prisma /usr/local/bin/docker-entrypoint.sh: line 8: 9 Aborted node /app/collector/index.js ``` Problem: container start up failed immediatly. ### Are there known steps to reproduce? _No response_
yindo added the needs info / can't replicate label 2026-02-22 18:24:32 -05:00
yindo closed this issue 2026-02-22 18:24:32 -05:00
Author
Owner

@timothycarambat commented on GitHub (Aug 15, 2024):

This is most likely related to your host machine. Does the docker container have sufficient resources?
docker stats [container_id]

If you have very low CPU or RAM I can imagine thread workers would fail - you would also have issues further along in the app regardless.

@timothycarambat commented on GitHub (Aug 15, 2024): This is most likely related to your host machine. Does the docker container have sufficient resources? `docker stats [container_id]` If you have very low CPU or RAM I can imagine thread workers would fail - you would also have issues further along in the app regardless.
Author
Owner

@tigflanker commented on GitHub (Aug 17, 2024):

@timothycarambat Hi Timothy, thank you for reply. Finally I haven't found reason why thread workers didn't work. But I noticed that my docker version can only update to 19.03. And that many docker contains worked abnormal on this condition.
I will update my system from CentOS7.6 to Ubuntu 22.04, and check it again.

@tigflanker commented on GitHub (Aug 17, 2024): @timothycarambat Hi Timothy, thank you for reply. Finally I haven't found reason why thread workers didn't work. But I noticed that my docker version can only update to 19.03. And that many docker contains worked abnormal on this condition. I will update my system from CentOS7.6 to Ubuntu 22.04, and check it again.
Author
Owner

@timothycarambat commented on GitHub (Aug 18, 2024):

Please let me know if upgrading Docker worked out. That docker version is quite old, but not that old

@timothycarambat commented on GitHub (Aug 18, 2024): Please let me know if upgrading Docker worked out. That docker version is quite old, but not _that_ old
Author
Owner

@Di-Zayn commented on GitHub (Oct 12, 2024):

@ tigflanker hello, I have met this problem too. Do you solve it?

@Di-Zayn commented on GitHub (Oct 12, 2024): @ tigflanker hello, I have met this problem too. Do you solve it?
yindo changed title from [BUG]: Meet some error when i start up a docker image to [GH-ISSUE #2120] [BUG]: Meet some error when i start up a docker image 2026-06-05 14:40:27 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#1382