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 #1265] [BUG]: Docker Compose crashes on getting response or opening workspace settings #791

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

Originally created by @iFloris on GitHub (May 2, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1265

How are you running AnythingLLM?

Docker (local)

What happened?

Since a few days my docker compose AnythingLLM setup crashes, whenever I ask for an LLM response in a thread or open workspace settings.

The following is shown in the docker logs:
anythingllm-1 | /usr/local/bin/docker-entrypoint.sh: line 7: 164 Illegal instruction (core dumped) node /app/server/index.js
anythingllm-1 exited with code 0

Docker compose restarts the container, but it keeps happening.
I use groq, but it also happens when connected to a local ollama.

What did I do to break things?

Are there known steps to reproduce?

This happens when I ask for any response in a thread or when I open workspace settings (url/workspace/workspace-name/settings/general-appearance).

Originally created by @iFloris on GitHub (May 2, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1265 ### How are you running AnythingLLM? Docker (local) ### What happened? Since a few days my docker compose AnythingLLM setup crashes, whenever I ask for an LLM response in a thread or open workspace settings. The following is shown in the docker logs: anythingllm-1 | /usr/local/bin/docker-entrypoint.sh: line 7: 164 Illegal instruction (core dumped) node /app/server/index.js anythingllm-1 exited with code 0 Docker compose restarts the container, but it keeps happening. I use groq, but it also happens when connected to a local ollama. What did I do to break things? ### Are there known steps to reproduce? This happens when I ask for any response in a thread or when I open workspace settings (url/workspace/workspace-name/settings/general-appearance).
yindo added the Dockerpossible bug labels 2026-02-22 18:21:23 -05:00
yindo closed this issue 2026-02-22 18:21:23 -05:00
yindo commented 2026-02-22 18:21:23 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 2, 2024):

What does your docker-compose look like? This seems like some directory or something is being mounted that should not be. Likely some library that should exist but isn't?

@timothycarambat commented on GitHub (May 2, 2024): What does your docker-compose look like? This seems like some directory or something is being mounted that should not be. Likely some library that should exist but isn't?
yindo commented 2026-02-22 18:21:23 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 2, 2024):

This has been reported before and this was the case see this SO comment

@timothycarambat commented on GitHub (May 2, 2024): This has been reported before and this was the case [see this SO comment]( https://stackoverflow.com/a/42159385 )
yindo commented 2026-02-22 18:21:23 -05:00
Author
Owner
Copy Link
Copy Source

@iFloris commented on GitHub (May 3, 2024):

Hi, thanks for getting back to me @timothycarambat you are right, it was docker compose related. I had a very simple custom docker compose setup, which apparently no longer works:

version: '3.8'
services:
  anythingllm:
    image: mintplexlabs/anythingllm:master
    ports:
      - "3001:3001"
    volumes:
      - ./storage:/app/server/storage
      - "./storage/.env:/app/server/.env"
    cap_add:
      - SYS_ADMIN
    restart: always

So I used the 'official' docker compose with build steps. I have copied over my sqlite db and assets dir to the server/storage folder. After fiddling with permissions, that now works too.

However, with the new docker compose configuration, I still get this:

[CommunicationKey] RSA key pair generated for signed payloads within AnythingLLM services.
Primary server in HTTP mode listening on port 3001
**/usr/local/bin/docker-entrypoint.sh: line 7:   163 Illegal instruction     (core dumped) node /app/server/index.js**
Collector hot directory and tmp storage wiped!
Document processor app listening on port 8888
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma

my docker compose now looks like this, which allows me to succesfully complete the build steps and start the application:

➜  docker git:(master) ✗ cat docker-compose.yml
version: "3.9"

name: anythingllm

networks:
  anything-llm:
    driver: bridge

services:
  anything-llm:
    restart: always
    container_name: anything-llm
    image: anything-llm:latest
    build:
      context: ../.
      dockerfile: ./docker/Dockerfile
      args:
        ARG_UID: ${UID:-1000}
        ARG_GID: ${GID:-1000}
    cap_add:
      - SYS_ADMIN
    volumes:
      - "./.env:/app/server/.env"
      - "../server/storage:/app/server/storage"
      - "../collector/hotdir/:/app/collector/hotdir"
      - "../collector/outputs/:/app/collector/outputs"
    user: "${UID:-1000}:${GID:-1000}"
    ports:
      - "3001:3001"
    env_file:
      - .env
    networks:
      - anything-llm
    extra_hosts:
      - "host.docker.internal:host-gateway"

I could well be wrong, but it does not seem to me I'm mounting directories incorrectly, as the build process completes succesfully for x86/x64?

➜  docker git:(master) ✗ docker compose build
WARN[0000] docker-compose.yml: `version` is obsolete
[+] Building 0.9s (38/38) FINISHED                                                                                                                                 docker:default
 => [anything-llm internal] load build definition from Dockerfile                                                                                                            0.0s
 => => transferring dockerfile: 7.21kB                                                                                                                                       0.0s
 => [anything-llm internal] load metadata for docker.io/library/ubuntu:jammy-20230916                                                                                        0.4s
 => [anything-llm internal] load .dockerignore                                                                                                                               0.0s
 => => transferring context: 418B                                                                                                                                            0.0s
 => [anything-llm internal] load build context                                                                                                                               0.1s
 => => transferring context: 56.59kB                                                                                                                                         0.1s
 => [anything-llm base 1/1] FROM docker.io/library/ubuntu:jammy-20230916@sha256:9b8dec3bf938bc80fbe758d856e96fdfab5f56c39d44b0cff351e847bb1b01ea                             0.0s
 => CACHED [anything-llm build-amd64 1/7] RUN echo "Preparing build of AnythingLLM image for non-ARM architecture"                                                           0.0s
 => CACHED [anything-llm build-amd64 2/7] RUN DEBIAN_FRONTEND=noninteractive apt-get update &&     DEBIAN_FRONTEND=noninteractive apt-get install -yq --no-install-recommen  0.0s
 => CACHED [anything-llm build-amd64 3/7] RUN groupadd -g "1000" anythingllm &&     useradd -l -u "1000" -m -d /app -s /bin/bash -g anythingllm anythingllm &&     mkdir -p  0.0s
 => CACHED [anything-llm build-amd64 4/7] COPY ./docker/docker-entrypoint.sh /usr/local/bin/                                                                                 0.0s
 => CACHED [anything-llm build-amd64 5/7] COPY ./docker/docker-healthcheck.sh /usr/local/bin/                                                                                0.0s
 => CACHED [anything-llm build-amd64 6/7] COPY --chown=anythingllm:anythingllm ./docker/.env.example /app/server/.env                                                        0.0s
 => CACHED [anything-llm build-amd64 7/7] RUN chmod +x /usr/local/bin/docker-entrypoint.sh &&     chmod +x /usr/local/bin/docker-healthcheck.sh                              0.0s
 => CACHED [anything-llm build 1/2] RUN echo "Running common build flow of AnythingLLM image for all architectures"                                                          0.0s
 => CACHED [anything-llm build 2/2] WORKDIR /app                                                                                                                             0.0s
 => CACHED [anything-llm server-deps 1/7] COPY ./server/package.json ./server/yarn.lock ./server/                                                                            0.0s
 => CACHED [anything-llm server-deps 2/7] WORKDIR /app/server                                                                                                                0.0s
 => CACHED [anything-llm server-deps 3/7] RUN yarn install --production --network-timeout 100000 && yarn cache clean                                                         0.0s
 => CACHED [anything-llm server-deps 4/7] WORKDIR /app                                                                                                                       0.0s
 => CACHED [anything-llm server-deps 5/7] WORKDIR /app/server                                                                                                                0.0s
 => CACHED [anything-llm server-deps 6/7] RUN npx --no node-llama-cpp download                                                                                               0.0s
 => CACHED [anything-llm server-deps 7/7] WORKDIR /app                                                                                                                       0.0s
 => CACHED [anything-llm production-stage 1/8] COPY --chown=anythingllm:anythingllm ./server/ ./server/                                                                      0.0s
 => CACHED [anything-llm frontend-deps 1/4] COPY ./frontend/package.json ./frontend/yarn.lock ./frontend/                                                                    0.0s
 => CACHED [anything-llm frontend-deps 2/4] WORKDIR /app/frontend                                                                                                            0.0s
 => CACHED [anything-llm frontend-deps 3/4] RUN yarn install --network-timeout 100000 && yarn cache clean                                                                    0.0s
 => CACHED [anything-llm frontend-deps 4/4] WORKDIR /app                                                                                                                     0.0s
 => CACHED [anything-llm build-stage 1/4] COPY ./frontend/ ./frontend/                                                                                                       0.0s
 => CACHED [anything-llm build-stage 2/4] WORKDIR /app/frontend                                                                                                              0.0s
 => CACHED [anything-llm build-stage 3/4] RUN yarn build && yarn cache clean                                                                                                 0.0s
 => CACHED [anything-llm build-stage 4/4] WORKDIR /app                                                                                                                       0.0s
 => CACHED [anything-llm production-stage 2/8] COPY --chown=anythingllm:anythingllm --from=build-stage /app/frontend/dist ./server/public                                    0.0s
 => CACHED [anything-llm production-stage 3/8] COPY --chown=anythingllm:anythingllm ./collector/ ./collector/                                                                0.0s
 => CACHED [anything-llm production-stage 4/8] WORKDIR /app/collector                                                                                                        0.0s
 => CACHED [anything-llm production-stage 5/8] RUN yarn install --production --network-timeout 100000 && yarn cache clean                                                    0.0s
 => CACHED [anything-llm production-stage 6/8] WORKDIR /app/server                                                                                                           0.0s
 => CACHED [anything-llm production-stage 7/8] RUN npx prisma generate --schema=./prisma/schema.prisma &&     npx prisma migrate deploy --schema=./prisma/schema.prisma      0.0s
 => CACHED [anything-llm production-stage 8/8] WORKDIR /app                                                                                                                  0.0s
 => [anything-llm] exporting to image                                                                                                                                        0.0s
 => => exporting layers                                                                                                                                                      0.0s
 => => writing image sha256:28085e5fb9233031a138385e109aa178205db9df8ff94afb7a9f756f022c615b                                                                                 0.0s
 => => naming to docker.io/library/anything-llm:latest
@iFloris commented on GitHub (May 3, 2024): Hi, thanks for getting back to me @timothycarambat you are right, it was docker compose related. I had a very simple custom docker compose setup, which apparently no longer works: ``` version: '3.8' services: anythingllm: image: mintplexlabs/anythingllm:master ports: - "3001:3001" volumes: - ./storage:/app/server/storage - "./storage/.env:/app/server/.env" cap_add: - SYS_ADMIN restart: always ``` So I used the 'official' docker compose with build steps. I have copied over my sqlite db and assets dir to the server/storage folder. After fiddling with permissions, that now works too. However, with the new docker compose configuration, I still get this: ``` [CommunicationKey] RSA key pair generated for signed payloads within AnythingLLM services. Primary server in HTTP mode listening on port 3001 **/usr/local/bin/docker-entrypoint.sh: line 7: 163 Illegal instruction (core dumped) node /app/server/index.js** Collector hot directory and tmp storage wiped! Document processor app listening on port 8888 Environment variables loaded from .env Prisma schema loaded from prisma/schema.prisma ``` my docker compose now looks like this, which allows me to succesfully complete the build steps and start the application: ``` ➜ docker git:(master) ✗ cat docker-compose.yml version: "3.9" name: anythingllm networks: anything-llm: driver: bridge services: anything-llm: restart: always container_name: anything-llm image: anything-llm:latest build: context: ../. dockerfile: ./docker/Dockerfile args: ARG_UID: ${UID:-1000} ARG_GID: ${GID:-1000} cap_add: - SYS_ADMIN volumes: - "./.env:/app/server/.env" - "../server/storage:/app/server/storage" - "../collector/hotdir/:/app/collector/hotdir" - "../collector/outputs/:/app/collector/outputs" user: "${UID:-1000}:${GID:-1000}" ports: - "3001:3001" env_file: - .env networks: - anything-llm extra_hosts: - "host.docker.internal:host-gateway" ``` I could well be wrong, but it does not seem to me I'm mounting directories incorrectly, as the build process completes succesfully for x86/x64? ``` ➜ docker git:(master) ✗ docker compose build WARN[0000] docker-compose.yml: `version` is obsolete [+] Building 0.9s (38/38) FINISHED docker:default => [anything-llm internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 7.21kB 0.0s => [anything-llm internal] load metadata for docker.io/library/ubuntu:jammy-20230916 0.4s => [anything-llm internal] load .dockerignore 0.0s => => transferring context: 418B 0.0s => [anything-llm internal] load build context 0.1s => => transferring context: 56.59kB 0.1s => [anything-llm base 1/1] FROM docker.io/library/ubuntu:jammy-20230916@sha256:9b8dec3bf938bc80fbe758d856e96fdfab5f56c39d44b0cff351e847bb1b01ea 0.0s => CACHED [anything-llm build-amd64 1/7] RUN echo "Preparing build of AnythingLLM image for non-ARM architecture" 0.0s => CACHED [anything-llm build-amd64 2/7] RUN DEBIAN_FRONTEND=noninteractive apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -yq --no-install-recommen 0.0s => CACHED [anything-llm build-amd64 3/7] RUN groupadd -g "1000" anythingllm && useradd -l -u "1000" -m -d /app -s /bin/bash -g anythingllm anythingllm && mkdir -p 0.0s => CACHED [anything-llm build-amd64 4/7] COPY ./docker/docker-entrypoint.sh /usr/local/bin/ 0.0s => CACHED [anything-llm build-amd64 5/7] COPY ./docker/docker-healthcheck.sh /usr/local/bin/ 0.0s => CACHED [anything-llm build-amd64 6/7] COPY --chown=anythingllm:anythingllm ./docker/.env.example /app/server/.env 0.0s => CACHED [anything-llm build-amd64 7/7] RUN chmod +x /usr/local/bin/docker-entrypoint.sh && chmod +x /usr/local/bin/docker-healthcheck.sh 0.0s => CACHED [anything-llm build 1/2] RUN echo "Running common build flow of AnythingLLM image for all architectures" 0.0s => CACHED [anything-llm build 2/2] WORKDIR /app 0.0s => CACHED [anything-llm server-deps 1/7] COPY ./server/package.json ./server/yarn.lock ./server/ 0.0s => CACHED [anything-llm server-deps 2/7] WORKDIR /app/server 0.0s => CACHED [anything-llm server-deps 3/7] RUN yarn install --production --network-timeout 100000 && yarn cache clean 0.0s => CACHED [anything-llm server-deps 4/7] WORKDIR /app 0.0s => CACHED [anything-llm server-deps 5/7] WORKDIR /app/server 0.0s => CACHED [anything-llm server-deps 6/7] RUN npx --no node-llama-cpp download 0.0s => CACHED [anything-llm server-deps 7/7] WORKDIR /app 0.0s => CACHED [anything-llm production-stage 1/8] COPY --chown=anythingllm:anythingllm ./server/ ./server/ 0.0s => CACHED [anything-llm frontend-deps 1/4] COPY ./frontend/package.json ./frontend/yarn.lock ./frontend/ 0.0s => CACHED [anything-llm frontend-deps 2/4] WORKDIR /app/frontend 0.0s => CACHED [anything-llm frontend-deps 3/4] RUN yarn install --network-timeout 100000 && yarn cache clean 0.0s => CACHED [anything-llm frontend-deps 4/4] WORKDIR /app 0.0s => CACHED [anything-llm build-stage 1/4] COPY ./frontend/ ./frontend/ 0.0s => CACHED [anything-llm build-stage 2/4] WORKDIR /app/frontend 0.0s => CACHED [anything-llm build-stage 3/4] RUN yarn build && yarn cache clean 0.0s => CACHED [anything-llm build-stage 4/4] WORKDIR /app 0.0s => CACHED [anything-llm production-stage 2/8] COPY --chown=anythingllm:anythingllm --from=build-stage /app/frontend/dist ./server/public 0.0s => CACHED [anything-llm production-stage 3/8] COPY --chown=anythingllm:anythingllm ./collector/ ./collector/ 0.0s => CACHED [anything-llm production-stage 4/8] WORKDIR /app/collector 0.0s => CACHED [anything-llm production-stage 5/8] RUN yarn install --production --network-timeout 100000 && yarn cache clean 0.0s => CACHED [anything-llm production-stage 6/8] WORKDIR /app/server 0.0s => CACHED [anything-llm production-stage 7/8] RUN npx prisma generate --schema=./prisma/schema.prisma && npx prisma migrate deploy --schema=./prisma/schema.prisma 0.0s => CACHED [anything-llm production-stage 8/8] WORKDIR /app 0.0s => [anything-llm] exporting to image 0.0s => => exporting layers 0.0s => => writing image sha256:28085e5fb9233031a138385e109aa178205db9df8ff94afb7a9f756f022c615b 0.0s => => naming to docker.io/library/anything-llm:latest ```
yindo commented 2026-02-22 18:21:23 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 3, 2024):

No that seems correct to me. Are you building on and ARM device? I think by default, unless specified, docker compose will build in compatibility mode, but since our dockerfile supports both arch's it should enable autodetection.

What chip arch are you on?

@timothycarambat commented on GitHub (May 3, 2024): No that seems correct to me. Are you building on and ARM device? I think by default, unless specified, docker compose will build in compatibility mode, but since our dockerfile supports both arch's it should enable autodetection. What chip arch are you on?
yindo commented 2026-02-22 18:21:23 -05:00
Author
Owner
Copy Link
Copy Source

@iFloris commented on GitHub (May 3, 2024):

Hello @timothycarambat this is on a Xeon server.

@iFloris commented on GitHub (May 3, 2024): Hello @timothycarambat this is on a Xeon server.
yindo commented 2026-02-22 18:21:24 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 3, 2024):

Then that makes sense, Xeon is x86, not arm so it makes sense to only build for amd64

@timothycarambat commented on GitHub (May 3, 2024): Then that makes sense, Xeon is x86, not arm so it makes sense to only build for amd64
yindo commented 2026-02-22 18:21:24 -05:00
Author
Owner
Copy Link
Copy Source

@iFloris commented on GitHub (May 3, 2024):

So this is interesting, I copied my (original, simple) docker compose file to another server and AnythingLLM works there.
The difference:

This currently works:

OS: Debian GNU/Linux 10 (buster) x86_64
Host: KVM RHEL-8.6.0 PC (Q35 + ICH9, 2009)
CPU: Intel Xeon Silver 4216 (24) @ 2.099GHz
Memory: 10240MiB / 257696 MiB
Docker Compose version v2.27.0
Docker version 26.1.1, build 4cf5afa

This does not:

OS: Proxmox VE 8.2.2 x86_64
Host: BANFF12 [baremetal]
CPU: Intel Xeon E5-2670 0 (64) @ 2.600GHz
Memory: 92153MiB / 257572 MiB
Docker Compose version v2.27.0
Docker version 26.1.1, build 4cf5afa

So I updated my dns to point to this server instead, but it's still a pretty weird problem.

@iFloris commented on GitHub (May 3, 2024): So this is interesting, I copied my (original, simple) docker compose file to another server and AnythingLLM works there. The difference: This currently works: ``` OS: Debian GNU/Linux 10 (buster) x86_64 Host: KVM RHEL-8.6.0 PC (Q35 + ICH9, 2009) CPU: Intel Xeon Silver 4216 (24) @ 2.099GHz Memory: 10240MiB / 257696 MiB Docker Compose version v2.27.0 Docker version 26.1.1, build 4cf5afa ``` This does not: ``` OS: Proxmox VE 8.2.2 x86_64 Host: BANFF12 [baremetal] CPU: Intel Xeon E5-2670 0 (64) @ 2.600GHz Memory: 92153MiB / 257572 MiB Docker Compose version v2.27.0 Docker version 26.1.1, build 4cf5afa ``` So I updated my dns to point to this server instead, but it's still a pretty weird problem.
yindo commented 2026-02-22 18:21:24 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 3, 2024):

While i cant nail down exactly why this occurs i can say that we have had issues reported with Proxmox before, but i dont have that system available to us so i cannot replicate to debug remotely, but i recall is was either permissions or port related

@timothycarambat commented on GitHub (May 3, 2024): While i cant nail down exactly why this occurs i can say that we have had issues reported with Proxmox before, but i dont have that system available to us so i cannot replicate to debug remotely, but i recall is was either permissions or port related
yindo commented 2026-02-22 18:21:24 -05:00
Author
Owner
Copy Link
Copy Source

@sbrosl commented on GitHub (May 3, 2024):

Hi Tim,

I am also experiencing this issue in a VM but using Hyper-V. This showed up when I pulled the :latest docker image two days ago. I don't build the project just use the image. I tried removing the /app/server/storage volume from the docker-compose file to be sure its not my folder giving permission issues and the issue persist with that being freshly populated by the image.

I've turned on debug logging for node, here are the last lines before the error

anything-llm  | MODULE 102: looking for ["/app/server/node_modules/apache-arrow"]
anything-llm  | MODULE 102: Module._load REQUEST ./util/buffer.js parent: /app/server/node_modules/apache-arrow/Arrow.js
anything-llm  | MODULE 102: RELATIVE: requested: ./util/buffer.js from parent.id /app/server/node_modules/apache-arrow/Arrow.js
anything-llm  | MODULE 102: looking for ["/app/server/node_modules/apache-arrow"]
anything-llm  | MODULE 102: Module._load REQUEST ./util/vector.js parent: /app/server/node_modules/apache-arrow/Arrow.js
anything-llm  | MODULE 102: Module._load REQUEST ./util/pretty.js parent: /app/server/node_modules/apache-arrow/Arrow.js
anything-llm  | MODULE 102: RELATIVE: requested: ./util/pretty.js from parent.id /app/server/node_modules/apache-arrow/Arrow.js
anything-llm  | MODULE 102: looking for ["/app/server/node_modules/apache-arrow"]
anything-llm  | MODULE 102: Module._load REQUEST ./visitor/typecomparator.js parent: /app/server/node_modules/apache-arrow/Arrow.js
anything-llm  | MODULE 102: Module._load REQUEST ./Arrow.js parent: /app/server/node_modules/apache-arrow/Arrow.dom.js
anything-llm  | MODULE 102: Module._load REQUEST ./arrow parent: /app/server/node_modules/vectordb/dist/index.js
anything-llm  | MODULE 102: RELATIVE: requested: ./arrow from parent.id /app/server/node_modules/vectordb/dist/index.js
anything-llm  | MODULE 102: looking for ["/app/server/node_modules/vectordb/dist"]
anything-llm  | MODULE 102: load "/app/server/node_modules/vectordb/dist/arrow.js" for module "/app/server/node_modules/vectordb/dist/arrow.js"
anything-llm  | MODULE 102: Module._load REQUEST apache-arrow parent: /app/server/node_modules/vectordb/dist/arrow.js
anything-llm  | MODULE 102: Module._load REQUEST ./remote parent: /app/server/node_modules/vectordb/dist/index.js
anything-llm  | MODULE 102: RELATIVE: requested: ./remote from parent.id /app/server/node_modules/vectordb/dist/index.js
anything-llm  | MODULE 102: looking for ["/app/server/node_modules/vectordb/dist"]
anything-llm  | MODULE 102: load "/app/server/node_modules/vectordb/dist/remote/index.js" for module "/app/server/node_modules/vectordb/dist/remote/index.js"
anything-llm  | MODULE 102: Module._load REQUEST ../index parent: /app/server/node_modules/vectordb/dist/remote/index.js
anything-llm  | MODULE 102: RELATIVE: requested: ../index from parent.id /app/server/node_modules/vectordb/dist/remote/index.js
anything-llm  | MODULE 102: looking for ["/app/server/node_modules/vectordb/dist/remote"]
anything-llm  | MODULE 102: Module._load REQUEST ../query parent: /app/server/node_modules/vectordb/dist/remote/index.js
anything-llm  | MODULE 102: RELATIVE: requested: ../query from parent.id /app/server/node_modules/vectordb/dist/remote/index.js
anything-llm  | MODULE 102: looking for ["/app/server/node_modules/vectordb/dist/remote"]
anything-llm  | MODULE 102: load "/app/server/node_modules/vectordb/dist/query.js" for module "/app/server/node_modules/vectordb/dist/query.js"
anything-llm  | MODULE 102: Module._load REQUEST apache-arrow parent: /app/server/node_modules/vectordb/dist/query.js
anything-llm  | MODULE 102: Module._load REQUEST ../native.js parent: /app/server/node_modules/vectordb/dist/query.js
anything-llm  | MODULE 102: RELATIVE: requested: ../native.js from parent.id /app/server/node_modules/vectordb/dist/query.js
anything-llm  | MODULE 102: looking for ["/app/server/node_modules/vectordb/dist"]
anything-llm  | MODULE 102: load "/app/server/node_modules/vectordb/native.js" for module "/app/server/node_modules/vectordb/native.js"
anything-llm  | MODULE 102: Module._load REQUEST @neon-rs/load parent: /app/server/node_modules/vectordb/native.js
anything-llm  | MODULE 102: looking for "@neon-rs/load" in ["/app/server/node_modules/vectordb/node_modules","/app/server/node_modules","/app/node_modules","/node_modules","/app/.node_modules","/app/.node_libraries","/usr/lib/node"]
anything-llm  | MODULE 102: load "/app/server/node_modules/@neon-rs/load/dist/index.js" for module "/app/server/node_modules/@neon-rs/load/dist/index.js"
anything-llm  | MODULE 102: Module._load REQUEST ./index.node parent: /app/server/node_modules/vectordb/native.js
anything-llm  | MODULE 102: RELATIVE: requested: ./index.node from parent.id /app/server/node_modules/vectordb/native.js
anything-llm  | MODULE 102: looking for ["/app/server/node_modules/vectordb"]
anything-llm  | MODULE 102: Module._load REQUEST @lancedb/vectordb-linux-x64-gnu parent: /app/server/node_modules/vectordb/native.js
anything-llm  | MODULE 102: looking for "@lancedb/vectordb-linux-x64-gnu" in ["/app/server/node_modules/vectordb/node_modules","/app/server/node_modules","/app/node_modules","/node_modules","/app/.node_modules","/app/.node_libraries","/usr/lib/node"]
anything-llm  | MODULE 102: load "/app/server/node_modules/@lancedb/vectordb-linux-x64-gnu/index.node" for module "/app/server/node_modules/@lancedb/vectordb-linux-x64-gnu/index.node"
anything-llm  | /usr/local/bin/docker-entrypoint.sh: line 7:   102 Illegal instruction     (core dumped) node /app/server/index.js
anything-llm exited with code 132

Let me know if there's anything you'd like me to run or test to help figure out the issue
Thanks!

@sbrosl commented on GitHub (May 3, 2024): Hi Tim, I am also experiencing this issue in a VM but using Hyper-V. This showed up when I pulled the :latest docker image two days ago. I don't build the project just use the image. I tried removing the /app/server/storage volume from the docker-compose file to be sure its not my folder giving permission issues and the issue persist with that being freshly populated by the image. I've turned on debug logging for node, here are the last lines before the error ``` anything-llm | MODULE 102: looking for ["/app/server/node_modules/apache-arrow"] anything-llm | MODULE 102: Module._load REQUEST ./util/buffer.js parent: /app/server/node_modules/apache-arrow/Arrow.js anything-llm | MODULE 102: RELATIVE: requested: ./util/buffer.js from parent.id /app/server/node_modules/apache-arrow/Arrow.js anything-llm | MODULE 102: looking for ["/app/server/node_modules/apache-arrow"] anything-llm | MODULE 102: Module._load REQUEST ./util/vector.js parent: /app/server/node_modules/apache-arrow/Arrow.js anything-llm | MODULE 102: Module._load REQUEST ./util/pretty.js parent: /app/server/node_modules/apache-arrow/Arrow.js anything-llm | MODULE 102: RELATIVE: requested: ./util/pretty.js from parent.id /app/server/node_modules/apache-arrow/Arrow.js anything-llm | MODULE 102: looking for ["/app/server/node_modules/apache-arrow"] anything-llm | MODULE 102: Module._load REQUEST ./visitor/typecomparator.js parent: /app/server/node_modules/apache-arrow/Arrow.js anything-llm | MODULE 102: Module._load REQUEST ./Arrow.js parent: /app/server/node_modules/apache-arrow/Arrow.dom.js anything-llm | MODULE 102: Module._load REQUEST ./arrow parent: /app/server/node_modules/vectordb/dist/index.js anything-llm | MODULE 102: RELATIVE: requested: ./arrow from parent.id /app/server/node_modules/vectordb/dist/index.js anything-llm | MODULE 102: looking for ["/app/server/node_modules/vectordb/dist"] anything-llm | MODULE 102: load "/app/server/node_modules/vectordb/dist/arrow.js" for module "/app/server/node_modules/vectordb/dist/arrow.js" anything-llm | MODULE 102: Module._load REQUEST apache-arrow parent: /app/server/node_modules/vectordb/dist/arrow.js anything-llm | MODULE 102: Module._load REQUEST ./remote parent: /app/server/node_modules/vectordb/dist/index.js anything-llm | MODULE 102: RELATIVE: requested: ./remote from parent.id /app/server/node_modules/vectordb/dist/index.js anything-llm | MODULE 102: looking for ["/app/server/node_modules/vectordb/dist"] anything-llm | MODULE 102: load "/app/server/node_modules/vectordb/dist/remote/index.js" for module "/app/server/node_modules/vectordb/dist/remote/index.js" anything-llm | MODULE 102: Module._load REQUEST ../index parent: /app/server/node_modules/vectordb/dist/remote/index.js anything-llm | MODULE 102: RELATIVE: requested: ../index from parent.id /app/server/node_modules/vectordb/dist/remote/index.js anything-llm | MODULE 102: looking for ["/app/server/node_modules/vectordb/dist/remote"] anything-llm | MODULE 102: Module._load REQUEST ../query parent: /app/server/node_modules/vectordb/dist/remote/index.js anything-llm | MODULE 102: RELATIVE: requested: ../query from parent.id /app/server/node_modules/vectordb/dist/remote/index.js anything-llm | MODULE 102: looking for ["/app/server/node_modules/vectordb/dist/remote"] anything-llm | MODULE 102: load "/app/server/node_modules/vectordb/dist/query.js" for module "/app/server/node_modules/vectordb/dist/query.js" anything-llm | MODULE 102: Module._load REQUEST apache-arrow parent: /app/server/node_modules/vectordb/dist/query.js anything-llm | MODULE 102: Module._load REQUEST ../native.js parent: /app/server/node_modules/vectordb/dist/query.js anything-llm | MODULE 102: RELATIVE: requested: ../native.js from parent.id /app/server/node_modules/vectordb/dist/query.js anything-llm | MODULE 102: looking for ["/app/server/node_modules/vectordb/dist"] anything-llm | MODULE 102: load "/app/server/node_modules/vectordb/native.js" for module "/app/server/node_modules/vectordb/native.js" anything-llm | MODULE 102: Module._load REQUEST @neon-rs/load parent: /app/server/node_modules/vectordb/native.js anything-llm | MODULE 102: looking for "@neon-rs/load" in ["/app/server/node_modules/vectordb/node_modules","/app/server/node_modules","/app/node_modules","/node_modules","/app/.node_modules","/app/.node_libraries","/usr/lib/node"] anything-llm | MODULE 102: load "/app/server/node_modules/@neon-rs/load/dist/index.js" for module "/app/server/node_modules/@neon-rs/load/dist/index.js" anything-llm | MODULE 102: Module._load REQUEST ./index.node parent: /app/server/node_modules/vectordb/native.js anything-llm | MODULE 102: RELATIVE: requested: ./index.node from parent.id /app/server/node_modules/vectordb/native.js anything-llm | MODULE 102: looking for ["/app/server/node_modules/vectordb"] anything-llm | MODULE 102: Module._load REQUEST @lancedb/vectordb-linux-x64-gnu parent: /app/server/node_modules/vectordb/native.js anything-llm | MODULE 102: looking for "@lancedb/vectordb-linux-x64-gnu" in ["/app/server/node_modules/vectordb/node_modules","/app/server/node_modules","/app/node_modules","/node_modules","/app/.node_modules","/app/.node_libraries","/usr/lib/node"] anything-llm | MODULE 102: load "/app/server/node_modules/@lancedb/vectordb-linux-x64-gnu/index.node" for module "/app/server/node_modules/@lancedb/vectordb-linux-x64-gnu/index.node" anything-llm | /usr/local/bin/docker-entrypoint.sh: line 7: 102 Illegal instruction (core dumped) node /app/server/index.js anything-llm exited with code 132 ``` Let me know if there's anything you'd like me to run or test to help figure out the issue Thanks!
yindo commented 2026-02-22 18:21:24 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 3, 2024):

This issue is because the default lancedb vector db does not have support (or can determine) which binary it needs to run lancedb.

vectordb@0.4.11:
  version "0.4.11"
  resolved "https://registry.yarnpkg.com/vectordb/-/vectordb-0.4.11.tgz#e5b209fc15fb100d8495c132d0e4cc817dc9065a"
  integrity sha512-hbN1qO08xdhEpoGecWR6UuvfnNFYDgZLvuEDvgq5nFVbA4er5qXTcEyxjnlTzKsVqFGLlPF+91I+JIigneX24w==
  dependencies:
    "@apache-arrow/ts" "^14.0.2"
    "@neon-rs/load" "^0.0.74"
    apache-arrow "^14.0.2"
    axios "^1.4.0"
  optionalDependencies:
    "@lancedb/vectordb-darwin-arm64" "0.4.11"
    "@lancedb/vectordb-darwin-x64" "0.4.11"
    "@lancedb/vectordb-linux-arm64-gnu" "0.4.11"
    "@lancedb/vectordb-linux-x64-gnu" "0.4.11"
    "@lancedb/vectordb-win32-x64-msvc" "0.4.11"

i would imagine linux x64 would be right?

@timothycarambat commented on GitHub (May 3, 2024): This issue is because the default `lancedb` vector db does not have support (or can determine) which binary it needs to run lancedb. ``` vectordb@0.4.11: version "0.4.11" resolved "https://registry.yarnpkg.com/vectordb/-/vectordb-0.4.11.tgz#e5b209fc15fb100d8495c132d0e4cc817dc9065a" integrity sha512-hbN1qO08xdhEpoGecWR6UuvfnNFYDgZLvuEDvgq5nFVbA4er5qXTcEyxjnlTzKsVqFGLlPF+91I+JIigneX24w== dependencies: "@apache-arrow/ts" "^14.0.2" "@neon-rs/load" "^0.0.74" apache-arrow "^14.0.2" axios "^1.4.0" optionalDependencies: "@lancedb/vectordb-darwin-arm64" "0.4.11" "@lancedb/vectordb-darwin-x64" "0.4.11" "@lancedb/vectordb-linux-arm64-gnu" "0.4.11" "@lancedb/vectordb-linux-x64-gnu" "0.4.11" "@lancedb/vectordb-win32-x64-msvc" "0.4.11" ``` i would imagine linux x64 would be right?
yindo commented 2026-02-22 18:21:24 -05:00
Author
Owner
Copy Link
Copy Source

@iFloris commented on GitHub (May 4, 2024):

This issue is because the default lancedb vector db does not have support (or can determine) which binary it needs to run lancedb.

i would imagine linux x64 would be right?

That's interesting, so the problem originated in the vectordb. That would explain why the web ui crashed when opening workspace settings.

Yes, I believe that linux x64 is right.
The machine that doesn't work (bare metal):
Linux 6.8.4-2-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.4-2 (2024-04-10T17:36Z) x86_64 GNU/Linux
and the KVM that does work:
Linux 4.19.0-26-amd64 #1 SMP Debian 4.19.304-1 (2024-01-09) x86_64 GNU/Linux

@iFloris commented on GitHub (May 4, 2024): > This issue is because the default `lancedb` vector db does not have support (or can determine) which binary it needs to run lancedb. > i would imagine linux x64 would be right? That's interesting, so the problem originated in the vectordb. That would explain why the web ui crashed when opening workspace settings. Yes, I believe that linux x64 is right. The machine that doesn't work (bare metal): `Linux 6.8.4-2-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.4-2 (2024-04-10T17:36Z) x86_64 GNU/Linux` and the KVM that does work: `Linux 4.19.0-26-amd64 #1 SMP Debian 4.19.304-1 (2024-01-09) x86_64 GNU/Linux`
yindo commented 2026-02-22 18:21:24 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 4, 2024):

This seems like now more of a support issue for https://github.com/lancedb/lancedb

That being said, we are on package 0.4.11 so it is possible could have been fixed since in the SDK. Obviously such a critical piece like the vectordb we have to bump very carefully.

@timothycarambat commented on GitHub (May 4, 2024): This seems like now more of a support issue for https://github.com/lancedb/lancedb That being said, we are on package `0.4.11` so it is possible could have been fixed since in the SDK. Obviously such a critical piece like the vectordb we have to bump very carefully.
yindo commented 2026-02-22 18:21:24 -05:00
Author
Owner
Copy Link
Copy Source

@iFloris commented on GitHub (May 5, 2024):

Yes, I think you are right @timothycarambat. Thanks for the help investigating and the great tool!

@iFloris commented on GitHub (May 5, 2024): Yes, I think you are right @timothycarambat. Thanks for the help investigating and the great tool!
yindo commented 2026-02-22 18:21:24 -05:00
Author
Owner
Copy Link
Copy Source

@sbrosl commented on GitHub (May 6, 2024):

Hi @timothycarambat,

I can confirm that I am on Linux x64 as well and the project is running in a podman container.

Could I suggest tagging the docker images with release versions like the desktop app? Simply so we could roll back in case of issues like this arising. Right now our instance is broken; even with no documents uploaded it crashes because of the default integrated LanceDB. The best option to "fix" this seems to be setting up an alternative vectordb (which is the route I am currently taking, two issues throwing the same error are currently open on the LanceDB repo since oct-nov of 2023 (https://github.com/lancedb/lancedb/issues/592 and https://github.com/lancedb/lancedb/issues/631) so I'm not sure Anything-LLM will start working for us with lancedb anytime soon).

Let me know if there is anything I can do to help. I'd like to echo iFloris and thank you and the community for the amazing open source project that is Anything-LLM!

@sbrosl commented on GitHub (May 6, 2024): Hi @timothycarambat, I can confirm that I am on Linux x64 as well and the project is running in a podman container. Could I suggest tagging the docker images with release versions like the desktop app? Simply so we could roll back in case of issues like this arising. Right now our instance is broken; even with no documents uploaded it crashes because of the default integrated LanceDB. The best option to "fix" this seems to be setting up an alternative vectordb (which is the route I am currently taking, two issues throwing the same error are currently open on the LanceDB repo since oct-nov of 2023 (https://github.com/lancedb/lancedb/issues/592 and https://github.com/lancedb/lancedb/issues/631) so I'm not sure Anything-LLM will start working for us with lancedb anytime soon). Let me know if there is anything I can do to help. I'd like to echo iFloris and thank you and the community for the amazing open source project that is Anything-LLM!
yindo commented 2026-02-22 18:21:24 -05:00
Author
Owner
Copy Link
Copy Source

@computersrmyfriends commented on GitHub (May 23, 2024):

I have the same issue. Does not work on XEON E5 2660

image

@computersrmyfriends commented on GitHub (May 23, 2024): I have the same issue. Does not work on XEON E5 2660 ![image](https://github.com/Mintplex-Labs/anything-llm/assets/323931/50d533d3-33af-4857-828b-e4ea67e9e82a)
yindo commented 2026-02-22 18:21:24 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 23, 2024):

@computersrmyfriends use the non-native embedder. ONNX cannot run on your CPU, so native model running will not work.

@timothycarambat commented on GitHub (May 23, 2024): @computersrmyfriends use the non-native embedder. ONNX cannot run on your CPU, so native model running will not work.
yindo commented 2026-02-22 18:21:24 -05:00
Author
Owner
Copy Link
Copy Source

@computersrmyfriends commented on GitHub (May 23, 2024):

Thank you for the response @timothycarambat . I will try that

@computersrmyfriends commented on GitHub (May 23, 2024): Thank you for the response @timothycarambat . I will try that
yindo commented 2026-02-22 18:21:24 -05:00
Author
Owner
Copy Link
Copy Source

@computersrmyfriends commented on GitHub (May 23, 2024):

image

I think you meant this ☝ @timothycarambat . I changed it.

But,even after that, once I send a message "hi" to the model on the workspace, it crashes,,,,

image

image

@computersrmyfriends commented on GitHub (May 23, 2024): ![image](https://github.com/Mintplex-Labs/anything-llm/assets/323931/bf050863-f666-4cab-8cfd-d7e597766563) I think you meant this ☝ @timothycarambat . I changed it. But,even after that, once I send a message "hi" to the model on the workspace, it crashes,,,, ![image](https://github.com/Mintplex-Labs/anything-llm/assets/323931/ec805272-0289-4cf2-b7fb-98e5dfc5c596) ![image](https://github.com/Mintplex-Labs/anything-llm/assets/323931/b9a130bd-57db-43f9-a049-243547677cf7)
yindo commented 2026-02-22 18:21:24 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 23, 2024):

Does sending a chat on an empty workspace work? Should not run any command on the embedder or vectordb. Referring to the thread, it looks like an invalid binary from lanceDB if the embedder can be ruled out

@timothycarambat commented on GitHub (May 23, 2024): Does sending a chat on an empty workspace work? Should not run any command on the embedder or vectordb. Referring to the thread, it looks like an invalid binary from lanceDB if the embedder can be ruled out
yindo commented 2026-02-22 18:21:24 -05:00
Author
Owner
Copy Link
Copy Source

@computersrmyfriends commented on GitHub (May 23, 2024):

Thanks for the super quick response.

image

The moment i created the workspace, it crashed again.

Then, i sent hi to the new workspace after restarting the container..., it crashed again..
image

@computersrmyfriends commented on GitHub (May 23, 2024): Thanks for the super quick response. ![image](https://github.com/Mintplex-Labs/anything-llm/assets/323931/cfdf677b-1597-4f97-87c7-f0c39e1ff920) The moment i created the workspace, it crashed again. Then, i sent hi to the new workspace after restarting the container..., it crashed again.. ![image](https://github.com/Mintplex-Labs/anything-llm/assets/323931/9f212643-efe1-456d-a6e3-b4b1a7325d14)
yindo commented 2026-02-22 18:21:25 -05:00
Author
Owner
Copy Link
Copy Source

@computersrmyfriends commented on GitHub (May 23, 2024):

@timothycarambat Now, I tried chromadb...

It does not crash now. So, the crashing issue was due to the inbuilt Vectordb.

But, it gives me this error:

image

@computersrmyfriends commented on GitHub (May 23, 2024): @timothycarambat Now, I tried chromadb... It does not crash now. So, the crashing issue was due to the inbuilt Vectordb. But, it gives me this error: ![image](https://github.com/Mintplex-Labs/anything-llm/assets/323931/d08229c1-3da9-4b73-b0d3-b340577dbe8e)
yindo commented 2026-02-22 18:21:25 -05:00
Author
Owner
Copy Link
Copy Source

@computersrmyfriends commented on GitHub (May 23, 2024):

image

@timothycarambat I tried creating another new workspace. With chromadb, it seems to be some different issue. it was giving an error twice and then it crashed.

@computersrmyfriends commented on GitHub (May 23, 2024): ![image](https://github.com/Mintplex-Labs/anything-llm/assets/323931/a5c3c880-8ead-4ab3-a079-a3e30f0ed039) @timothycarambat I tried creating another new workspace. With chromadb, it seems to be some different issue. it was giving an error twice and then it crashed.
yindo commented 2026-02-22 18:21:25 -05:00
Author
Owner
Copy Link
Copy Source

@computersrmyfriends commented on GitHub (May 23, 2024):

Also errors from chromadb container if it might help:

image

@computersrmyfriends commented on GitHub (May 23, 2024): Also errors from chromadb container if it might help: ![image](https://github.com/Mintplex-Labs/anything-llm/assets/323931/9750a3dd-387b-4ae2-9d0b-3b291acdec9f)
yindo changed title from [BUG]: Docker Compose crashes on getting response or opening workspace settings to [GH-ISSUE #1265] [BUG]: Docker Compose crashes on getting response or opening workspace settings 2026-06-05 14:37:13 -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 Docker 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#791
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?