-
Notifications
You must be signed in to change notification settings - Fork 4
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
embedded_py option #10
Comments
Hi, Currently there are two ways to do this for each database individually but not for the database farm itself: For the first way you need to set a daemon password when you create the image. Something like: This will create the default database Then from the host you can run Alternatively, you can access the shell inside the container, after you start it, using Now, by testing all this when writing this comment, I realized that numpy is missing from the image, so the databases cannot start with embedded python. This will be corrected, but in the meantime I suggest that you use the second way and install numpy with the command |
Hello, Thank you for your reply. This is indeed the normal way to do it, however, in Docker, it should be in the entry point. I managed to run the database farm by editing the last line of "scripts/entrypoint.sh" by running it using "mserver5" command, and adding "dnf install python3-numpy" in Dockerfile. Maybe you could add an option in the run of the container to allow the user to activate embedpy3. Thank you for your great work. Regards |
Yes I agree. I am thinking that we should probably add another environment variable that sets database farm options and/or database options. Thank you for the feedback! |
Small update on this: the rpm should now pull the numpy package when it gets installed: MonetDB/MonetDB@8a27b36 This will take effect in the next bugfix release. In the meantime I will change the Dockerfile so that it explicitly installs |
Hello,
I think it would be good to give the option to run the MonetDB with embedded_py
Cheers
The text was updated successfully, but these errors were encountered: