LibreChat-dev container fails to start #7918
Replies: 2 comments 1 reply
-
In general, we do not recommend using the devcontainer as we don't actively maintain it. There are some open PRs addressing some of the issues (not yet merged since there's other issues with them): For recommended development options, see: |
Beta Was this translation helpful? Give feedback.
-
The error you're encountering is due to file system permission issues inside the container when LibreChat tries to create a log directory:
✅ Root Cause In newer versions of the LibreChat Docker image, the backend tries to write logs to /app/packages/data-schemas/logs/, but the directory either doesn't exist or the container user doesn’t have permission to create it. This wasn't an issue in older builds, likely because: Logging wasn't configured the same way. Or the permissions were more permissive by default. ✅ Solution 1: Set Proper Volume Mount + Permissions You can ensure that the log directory is created and has the correct permissions: Step-by-step fix:
✅ Solution 2: Override the Container User (if needed) If mounting the volume doesn’t fix it, you may need to run the container as root:
However, this is not recommended unless you trust the container and know what you’re doing. Prefer setting proper permissions instead. ✅ Optional: Temporary Downgrade If you need an immediate workaround, stick to the last working image:
…but for long-term reliability, it’s better to fix the permission issue to remain compatible with updates. ✅ Bonus: Make it Resilient Across Updates To ensure this doesn’t break again with future updates: Check if logs path can be configured via env or config file (often possible with Winston). If the project allows overriding logger config, point it to a writable path like /tmp/logs. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
What happened?
I LibreChat via Docker compose and for the past few weeks the
api
/LibreChat
container will not start. The last image version that starts isghcr.io/danny-avila/librechat-dev@sha256:d27883cb774d2a73de5fd3941b47d14c73caf7209a3cef185c6f79a959de5a74
from 6-2.Version Information
sha256:d27883cb774d2a73de5fd3941b47d14c73caf7209a3cef185c6f79a959de5a74
Steps to Reproduce
Download any docker image newer than
ghcr.io/danny-avila/librechat-dev@sha256:d27883cb774d2a73de5fd3941b47d14c73caf7209a3cef185c6f79a959de5a74
What browsers are you seeing the problem on?
No response
Relevant log output
Screenshots
No response
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions