Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-20 14:43:37 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #1007] [BUG]: Container failed to start after pulling new image #618

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

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

How are you running AnythingLLM?

Docker (local)

What happened?

mintplexlabs/anythingllm:master DIGEST sha256:3f51ee794b9c1bfb51285d564e5c08d4bbb759affda6885cd570999ab3fdf802

Environment, CPU architecture, OS, and Version:
linux/amd64 on Linux debian 12 host, docker version 24.0.7

Docker compose file:

version: "3.9"

services:
  anything-llm:
    container_name: anything-llm
    image: mintplexlabs/anythingllm:latest
    cap_add:
      - SYS_ADMIN
    volumes:
      - storage:/app/server/storage
      - hotdir:/app/collector/hotdir
      - outputs:/app/collector/outputs
      - /var/lib/docker/volumes/llm_storage/_data/.env:/app/server/.env
    environment:
      - STORAGE_DIR:"/app/server/storage"
    ports:
      - "3001:3001"

volumes:
  storage:
  hotdir:
  outputs:

Describe the bug
After pulling new image AnythingLLM container does not start. Error from logs:

node:internal/validators:162
    throw new ERR_INVALID_ARG_TYPE(name, 'string', value);
    ^

TypeError [ERR_INVALID_ARG_TYPE]: The "paths[0]" argument must be of type string. Received undefined
    at new NodeError (node:internal/errors:405:5)
    at validateString (node:internal/validators:162:11)
    at Object.resolve (node:path:1097:7)
    at Object.<anonymous> (/app/collector/utils/comKey/index.js:8:12)
    at Module._compile (node:internal/modules/cjs/loader:1356:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)
    at Module.load (node:internal/modules/cjs/loader:1197:32)
    at Module._load (node:internal/modules/cjs/loader:1013:12)
    at Module.require (node:internal/modules/cjs/loader:1225:19)
    at require (node:internal/modules/helpers:177:18) {
  code: 'ERR_INVALID_ARG_TYPE'
}

Node.js v18.19.1

Additional context

Working fine on old image

Are there known steps to reproduce?

No response

Originally created by @fakezeta on GitHub (Apr 2, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1007 ### How are you running AnythingLLM? Docker (local) ### What happened? mintplexlabs/anythingllm:master DIGEST sha256:3f51ee794b9c1bfb51285d564e5c08d4bbb759affda6885cd570999ab3fdf802 **Environment, CPU architecture, OS, and Version:** linux/amd64 on Linux debian 12 host, docker version 24.0.7 Docker compose file: ``` version: "3.9" services: anything-llm: container_name: anything-llm image: mintplexlabs/anythingllm:latest cap_add: - SYS_ADMIN volumes: - storage:/app/server/storage - hotdir:/app/collector/hotdir - outputs:/app/collector/outputs - /var/lib/docker/volumes/llm_storage/_data/.env:/app/server/.env environment: - STORAGE_DIR:"/app/server/storage" ports: - "3001:3001" volumes: storage: hotdir: outputs: ``` **Describe the bug** After pulling new image AnythingLLM container does not start. Error from logs: ``` node:internal/validators:162 throw new ERR_INVALID_ARG_TYPE(name, 'string', value); ^ TypeError [ERR_INVALID_ARG_TYPE]: The "paths[0]" argument must be of type string. Received undefined at new NodeError (node:internal/errors:405:5) at validateString (node:internal/validators:162:11) at Object.resolve (node:path:1097:7) at Object.<anonymous> (/app/collector/utils/comKey/index.js:8:12) at Module._compile (node:internal/modules/cjs/loader:1356:14) at Module._extensions..js (node:internal/modules/cjs/loader:1414:10) at Module.load (node:internal/modules/cjs/loader:1197:32) at Module._load (node:internal/modules/cjs/loader:1013:12) at Module.require (node:internal/modules/cjs/loader:1225:19) at require (node:internal/modules/helpers:177:18) { code: 'ERR_INVALID_ARG_TYPE' } Node.js v18.19.1 ``` **Additional context** <!-- Add any other context about the problem here. --> Working fine on old image ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:20:29 -05:00
yindo closed this issue 2026-02-22 18:20:29 -05:00
yindo commented 2026-02-22 18:20:29 -05:00
Author
Owner
Copy Link
Copy Source

@fakezeta commented on GitHub (Apr 2, 2024):

Solved recreating the stack.

@fakezeta commented on GitHub (Apr 2, 2024): Solved recreating the stack.
yindo changed title from [BUG]: Container failed to start after pulling new image to [GH-ISSUE #1007] [BUG]: Container failed to start after pulling new image 2026-06-05 14:36:18 -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#618
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?