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
Difficult to figure out docker-compose #442
Comments
Hi @sidthekidder, Thanks for opening the issue. You can try to simply run |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm trying to run this project via docker-compose but I get some errors that I generally don't see in python libraries:
why do we need to include the entire source code in a separate parallel folder outside our project? Why can't we add mercury to our own existing docker-compose/Dockerfile via the regular requirements.txt? It is quite difficult to modify all services etc of a large project, just for one library - it is too opinionated (we don't use nginx nor postgres).
I get permission errors because it seems mercury tries to write files inside the /usr/src/python3.10/libraries/mercury folder. My docker user does not have write permissions across the entire image - I can't use root user here for security reasons. I also have a different base image.
Please solve these issues if possible and make it more suitable for production, I think mercury is a really helpful project overall!
The text was updated successfully, but these errors were encountered: