Fail to build docker commit: 9db3d792cc58e0fec321a26fc3da327e428d369a #1329
-
Contact DetailsNo response What happened?docker-compose build: WARN BADENGINE Steps to Reproducegit pull, docker-compose build. What browsers are you seeing the problem on?No response Relevant log outputNo response ScreenshotsNo response Code of Conduct
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 4 replies
-
I can't reproduce it. Try the following: # Stop the container (if running)
docker-compose down
# Fetch the latest changes from Github
git fetch origin
# Switch to the repo's main branch
git checkout main
# Pull the latest changes to the main branch from Github
git pull origin main
# Prune all LibreChat Docker images
docker rmi librechat:latest
# Remove all unused dangling Docker images
docker image prune -f
# Building a new LibreChat image
docker-compose build
# Start LibreChat
docker-compose up |
Beta Was this translation helpful? Give feedback.
-
I'm in the middle of updating a computer that was running on a commit dating back to June (last PR around #530). Will report back as it runs slow to update. |
Beta Was this translation helpful? Give feedback.
-
Nothing to worry about here. Vite is pushing this warning because we are on node v19 and it has reach its End of life, as it will no longer be maintained; therefore, vite will not raise concern over issues using this engine. This is very recent, and we will move to node:20-alpine instead of 19 soon once I can debug other unrelated issues related to this upgrade with the default compose file.
This indicates to me that the image is out of sync as is the same issue with the other discussion's issue I was able to reproduce the issue on a computer on an old commit and it's an issue with the compose file, should be fixed with this: #1330 |
Beta Was this translation helpful? Give feedback.
-
Same here. I tried "npm run update:docker" and here is the logs:
Tried as you suggest:
still no luck |
Beta Was this translation helpful? Give feedback.
Nothing to worry about here. Vite is pushing this warning because we are on node v19 and it has reach its End of life, as it will no longer be maintained; therefore, vite will not raise concern over issues using this engine. This is very recent, and we will move to node:20-alpine instead of 19 soon once I can debug other unrelated issues related to this upgrade with the default compose file.
This indicates to me that the image is out of sync as is the same issue with the other discussion's issue
Error: Cannot find module '/app/api/server/index.js'
(#776)I was able to reproduce the issue on a computer on an old commit and it'…