Skip to content
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

Fixed "no such group" error in Dockerfile, added docx2txt and cryptography deps #1841

Merged
merged 2 commits into from
Apr 19, 2024

Conversation

dividebysandwich
Copy link
Contributor

@dividebysandwich dividebysandwich commented Apr 10, 2024

Creating a docker container was giving me a "No such group" error for the worker group. This has been fixed.
Also, I have added docx2txt to poetry, so users no longer get the error that docx2txt is not installed when running privategpt in a docker container.
cryptography has been added as well to remove the error when trying to parse certain PDF files.

@dividebysandwich dividebysandwich changed the title Fixed "no such group" error in Dockerfile, added docx2txt to poetry Fixed "no such group" error in Dockerfile, added docx2txt and cryptography deps Apr 10, 2024
@imartinez imartinez merged commit 947e737 into zylon-ai:main Apr 19, 2024
5 of 6 checks passed
@@ -13,6 +13,8 @@ injector = "^0.21.0"
pyyaml = "^6.0.1"
watchdog = "^4.0.0"
transformers = "^4.38.2"
docx2txt = "^0.8"
cryptography = "^3.1"
Copy link

@drupol drupol Apr 21, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This new line is breaking local installation:

 > Checking runtime dependencies for private_gpt-0.5.0-py3-none-any.whl
 >   - cryptography<4.0,>=3.1 not satisfied by version 42.0.5

FYI, the current cryptography package is at version 42.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did not try it with version 42. I used 3.1 because that was specifically requested by other dependencies. I can give that a go tomorrow. But I tested both local installs and Docker on a blank VM and both worked. Still, using a more current version is probably better so I'll check if that works, of if the newest version causes any problems.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool, looking forward for that!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool, looking forward for that!

Appears to work fine.
See dividebysandwich@ef51645 - but I haven't tested very thoroughly. Please let me know if this solves your problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants