[Bug]: Unable to install with docker, container startup failed

[mwnu]

Contact Details

No response

What happened?

Container cannot start, error log: Error: Cannot find module '/app/api/server/index.js'

Steps to Reproduce

Neither bulid image nor docker hub image can be started, regardless of configuration.

What browsers are you seeing the problem on?

No response

Relevant log output

Node.js v19.9.0

}
  requireStack: []
  code: 'MODULE_NOT_FOUND',
    at node:internal/main/run_main_module:23:47 {
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
    at Module._load (node:internal/modules/cjs/loader:934:27)
    at Module._resolveFilename (node:internal/modules/cjs/loader:1090:15)
Error: Cannot find module '/app/api/server/index.js'

  ^
  throw err;
node:internal/modules/cjs/loader:1093

> cross-env NODE_ENV=production node api/server/index.js
> LibreChat@0.5.6 backend

Screenshots

Code of Conduct

• I agree to follow this project's Code of Conduct

[danny-avila]

Just did a clean installation and can't reproduce it.

I recommend you install git and npm and run npm run update:docker from the project directory.

[danny-avila]

Certainly don't mean to hijack anything, but, i can confirm i am having his exact same issue, same testing completed and can confirm that i'm able to git fetch origin and pull down the latest changes. Still broken.

Install npm if you don't have it already:

Navigate to https://nodejs.org/en/download and to download the latest Node.js version for your OS (The Node.js installer includes the NPM package manager.)

after it's installed and you're in the LibreChat directory, run npm run update:docker and please share your logs.

Also please share your docker version, Operating System version as well.

[danny-avila]

@bubbaMoose here are my logs after doing the above, no issues:

danny@MSI:~/LibreChat$ npm run update:docker

> LibreChat@0.6.1 update:docker
> node config/update.js -d

Starting update script, this may take a minute or two depending on your system and network.
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
Fetching the latest repo...
remote: Enumerating objects: 6, done.
remote: Counting objects: 100% (6/6), done.
remote: Compressing objects: 100% (6/6), done.
remote: Total 6 (delta 0), reused 3 (delta 0), pack-reused 0
Unpacking objects: 100% (6/6), 4.33 KiB | 4.33 MiB/s, done.
From https://github.com/danny-avila/LibreChat
   df1dfa7d..9db3d792  main       -> origin/main
 + 6c71d023...8bfd6e5e gh-pages   -> origin/gh-pages  (forced update)
Switching to main branch...
Already on 'main'
Your branch is behind 'origin/main' by 1 commit, and can be fast-forwarded.
  (use "git pull" to update your local branch)
Pulling the latest code from main...
From https://github.com/danny-avila/LibreChat
 * branch              main       -> FETCH_HEAD
Updating df1dfa7d..9db3d792
Fast-forward
 .env.example | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
Removing previously made Docker container...
docker-compose down
WARN[0000] The "UID" variable is not set. Defaulting to a blank string. 
WARN[0000] The "GID" variable is not set. Defaulting to a blank string. 
WARN[0000] The "UID" variable is not set. Defaulting to a blank string. 
WARN[0000] The "GID" variable is not set. Defaulting to a blank string. 
WARN[0000] The "UID" variable is not set. Defaulting to a blank string. 
WARN[0000] The "GID" variable is not set. Defaulting to a blank string. 
Pruning all LibreChat Docker images...
Untagged: librechat:latest
Deleted: sha256:184b4b2b260d496087e22c52937463a16b7c4d4e431b94d43e4b22098b8f2b96
Removing all unused dangling Docker images...
Deleted Images:
deleted: sha256:1260e6d5e2452f2da344e2b0ec94bf28314f22c45ae71dc63891b9981e9c4bc6
deleted: sha256:79ea96291d0140ebb511da68c0f177432ece5b071754e562d1eeccb35096734e
deleted: sha256:0352ca326d73ad1c9bc4ae7c9594d23585822bebb7906e37372982e91f195050
deleted: sha256:28ed3167e7d806e50e98d3087551efe71d5f089778ce8485858cbce6f26c29f7
deleted: sha256:8965643088ce54f76def07a7452a64799a03bfdd7b4a2d091d35df7f7a0a05f5
deleted: sha256:7db920932b31e0db37106f15b14a4ba47d1a7e0947a41cc479cf0b8c89824006
deleted: sha256:4a77ec967cdad2a3a117e7e771a2f32540391640fc4cdd9cfef118298b1a9ef4
deleted: sha256:cdd7a3f87f03b8901177f2ff8229ae568f966ea598e3fa97e9c4f7237835efdc

Total reclaimed space: 0B
Building new LibreChat image...
docker-compose build
WARN[0000] The "UID" variable is not set. Defaulting to a blank string. 
WARN[0000] The "GID" variable is not set. Defaulting to a blank string. 
WARN[0000] The "UID" variable is not set. Defaulting to a blank string. 
WARN[0000] The "GID" variable is not set. Defaulting to a blank string. 
WARN[0000] The "UID" variable is not set. Defaulting to a blank string. 
WARN[0000] The "GID" variable is not set. Defaulting to a blank string. 
[+] Building 48.9s (10/10) FINISHED                                                                                                                                                                                       
 => [internal] load build definition from Dockerfile                                                                                                                                                                 0.0s
 => => transferring dockerfile: 875B                                                                                                                                                                                 0.0s
 => [internal] load .dockerignore                                                                                                                                                                                    0.0s
 => => transferring context: 34B                                                                                                                                                                                     0.0s
 => [internal] load metadata for docker.io/library/node:19-alpine                                                                                                                                                    0.0s
 => [internal] load build context                                                                                                                                                                                    0.2s
 => => transferring context: 30.15MB                                                                                                                                                                                 0.2s
 => CACHED [1/5] FROM docker.io/library/node:19-alpine                                                                                                                                                               0.0s
 => [2/5] COPY . /app                                                                                                                                                                                                0.5s
 => [3/5] WORKDIR /app                                                                                                                                                                                               0.0s
 => [4/5] RUN apk --no-cache add curl &&     touch .env &&     npm ci                                                                                                                                               25.9s
 => [5/5] RUN npm run frontend                                                                                                                                                                                      16.7s
 => exporting to image                                                                                                                                                                                               5.4s 
 => => exporting layers                                                                                                                                                                                              5.4s 
 => => writing image sha256:6d5614c6a294e2a5399c1f30aee21d331507a40bf9e0189c470136680f8e3412                                                                                                                         0.0s 
 => => naming to docker.io/library/librechat                                                                                                                                                                         0.0s 
Your LibreChat app is now up to date! Start the app with the following command:                                                                                                                                           
docker-compose up                                                                                                                                                                                                         
Note: it's also recommended to clear your browser cookies and localStorage for LibreChat to assure a fully clean installation.
Also: Don't worry, your data is safe :)
danny@MSI:~/LibreDevMain$ docker-compose up
WARN[0000] The "UID" variable is not set. Defaulting to a blank string. 
WARN[0000] The "GID" variable is not set. Defaulting to a blank string. 
WARN[0000] The "UID" variable is not set. Defaulting to a blank string. 
WARN[0000] The "GID" variable is not set. Defaulting to a blank string. 
WARN[0000] The "UID" variable is not set. Defaulting to a blank string. 
WARN[0000] The "GID" variable is not set. Defaulting to a blank string. 
[+] Running 4/3
 ✔ Network libredevmain_default  Created                                                                                                                                                                             0.7s 
 ✔ Container chat-meilisearch    Created                                                                                                                                                                             0.1s 
 ✔ Container chat-mongodb        Created                                                                                                                                                                             0.1s 
 ✔ Container LibreChat           Created                                                                                                                                                                             0.1s 
Attaching to LibreChat, chat-meilisearch, chat-mongodb

2023-12-11 18:40:17 > LibreChat@0.6.1 backend
2023-12-11 18:40:17 > cross-env NODE_ENV=production node api/server/index.js
2023-12-11 18:40:17 
2023-12-11 18:40:19 Connected to MongoDB
2023-12-11 18:40:19 There are 18 messages in the database, 18 indexed
2023-12-11 18:40:19 There are 7 convos in the database, 7 indexed
2023-12-11 18:40:19 Server listening on all interfaces at port 3080. Use http://localhost:3080 to access it
2023-12-11 18:40:19 Warning: connect.session() MemoryStore is not
2023-12-11 18:40:19 designed for a production environment, as it will leak
2023-12-11 18:40:19 memory, and will not scale past a single process.

[danny-avila]

I followed the same steps on WSL2 Linux and Windows 11, both no issues:

2023-12-11 18:44:35 > LibreChat@0.6.1 backend
2023-12-11 18:44:35 > cross-env NODE_ENV=production node api/server/index.js
2023-12-11 18:44:35 
2023-12-11 18:44:44 Connected to MongoDB
2023-12-11 18:44:45 Server listening on all interfaces at port 3080. Use http://localhost:3080 to access it
2023-12-11 18:44:44 Warning: connect.session() MemoryStore is not
2023-12-11 18:44:44 designed for a production environment, as it will leak
2023-12-11 18:44:44 memory, and will not scale past a single process.

[id628]

Same here, using git repo. Same error.

[danny-avila]

@id628 read the comments I just posted and try to run this. Please share the exact steps that led you to the error, also any guides you've followed. This is the main guide: https://docs.librechat.ai/install/docker_compose_install.html

Also please share your docker version, Operating System version as well.

[pikaro]

Probably the same mistake I made, or at least something adjacent - the Compose file tells you to bind-mount "./api" which only works if you cloned the repo. If you want to run it like a Docker image is usually used, i. e. precisely without cloning the repo and instead pull the image from GHCR, it clears out the /app/api directory, resulting in the above error. If there is any data in that directory that requires persistence, the Compose file should specify the exact path, not the entire api folder.

[danny-avila]

do you mind editing the compose file, testing it, and submitting a PR?

[danny-avila]

I was able to reproduce this issue on a computer on an old commit. #1330 should fix this if you want to try again.

it's also important to use docker-compose build --no-cache to ensure the cache isn't being used

[danny-avila]

If you’re still having issues it may be due to local changes to the compose file.

To manage your changes in ./docker-compose.yml and update your repository, you'll need to use Git commands. Here's how you can do it:

1. Stash Your Changes: Save your current changes without committing them.

   git stash push -m "Your stash message" ./docker-compose.yml

   This command stashes the changes made to ./docker-compose.yml and keeps your working directory clean. The -m option allows you to add a custom message to your stash for easier identification later.

2. Pull the Latest Changes: Update your repository from the remote branch.

   git pull origin main

   This command fetches the latest changes from the main branch of the remote repository (assumed to be named origin) and merges them into your current branch.

3. Reapply Your Stashed Changes: Once the pull is complete, you can reapply the changes you stashed earlier.

   git stash pop

   This command applies the most recently stashed changes to your working directory and removes them from the stash list. If you want to keep the changes in the stash list, use git stash apply instead.

Remember to resolve any merge conflicts that may arise when you reapply your stashed changes. After resolving conflicts, you can continue working as usual.