gempy
gempy copied to clipboard
Error building Docker Image
Hi,
Because I had some issues with the installation process in MacOS, I tried building the Docker image myself from the dockerfile. However, the build failed with the following message:
Could not find a version that satisfies the requirement PyQt5-Qt5>=5.15.2 (from pyqt5->gempy) (from versions: ) #13 64.50 No matching distribution found for PyQt5-Qt5>=5.15.2 (from pyqt5->gempy)
I tried to use the leguark/gempy image but ran into some errors there too (see issue on dead Kernel with plot_3D).
Hi @snakesonabrain
for Mac, I have this gempy environment. I use it on my machine and currently working with also 3D plotting. https://github.com/Japhiolite/environments/blob/master/environment_gempy_mac2.yml
Hi @snakesonabrain
can you link to Miguels docker image? could not find a leguark/gempy repository.
Hi @snakesonabrain
can you link to Miguels docker image? could not find a leguark/gempy repository.
Where can I find this Docker image? The leguark/gempy image is the once which is mentioned in the installation guide.
Ah, I see. Thought you were trying the docker image. That might be a remnant in the documentation and the docker may (most likely will) not be up to date, if it still exists. I'll ask @Leguark .
Hi @snakesonabrain the docker image can be found here: https://hub.docker.com/r/leguark/gempy However, it might not work as it's pretty old...but maybe I'm mistaken and it works after all :)
Tried that one, but it returns an error when running the getting started jupyter notebook:
Just to clarify, you try running gempy in a jupyter notebook (and not, for instance, google colab) on which OS?
Indeed, just a local Jupyter notebook, opened from the Docker console. But it is the same issue.
My OS is MacOS Monterey 12.3 but the Docker image is based on Debian, I believe?
I have tried the docker image on another PC with Windows 10 as OS and it gives exactly the same error (as could be expected with Docker). So the image by @Leguark likely needs checking.
Docker is not supported anymore. We have axed most of gempy dependencies so hopefully we never need to go through the "add complexity" route to deal with complexity