-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latest container issue will not start #15
Comments
If it helps, the logs show this repeated for every restart : privategpt version: 0.5.0 And it restarts every 60 seconds. Dean. |
i think that is an upstream issue atm. i am currently on vacation. try running an older version instead. sry for that :/ |
Hi, Thanks for replying even on vacation ! After reading that article you linked to, i have changed your dockerfile for the latest version so that it installs numpy 1.26.0 and now it all builds and starts up as it should ! Thanks for your help with this ! Do you know if this latest PrivateGPT of yours includes the auto consumption of documents ? If the container gets restarted i need to re upload the docs at the moment. Have a great vacation and i am sure we will be in contact in a couple of weeks when you are back. Thanks. |
if 'KEEP_FILES' is 'true', which should be the default, the files should be available even after restart. |
Hello, Here is the error: 20:15:08.578 [INFO ] private_gpt.settings.settings_loader - Starting application with profiles=['default'] |
i implemented gemini and clickhouse support. |
Hi,
After pulling the "latest" version of the PrivateGPT container, the container just restarts every few seconds and doesnt stay running.
I can also see a traceback and numerous failed lines in the logs that are also repeated for every restart.
It is the same host that is running the container image from January this year .... are there any updates that are needed to the host for this current version to work ?
I have tried to build the container from the dockerfile too. It builds with no errors but has the same problem starting the container from the image.
Thanks.
Dean.
The text was updated successfully, but these errors were encountered: