search

Kitware / paraview-visualizer

Web frontend to ParaView based on trame
BSD 3-Clause "New" or "Revised" License
30 stars 12 forks source link

ModuleNotFoundError: No module named 'wslink' #15

Open PierreLouis94 opened 1 month ago

PierreLouis94 commented 1 month ago

I am trying to run the docker script that has been described in the docker folder. Instead of downloading paraview everytime I run the dockerfile, I have linked it to my local paraview binarie folder (ParaView-5.10.1-MPI-Linux-Python3.9-x86_64). The build seems to work great, as soon as the server image is run i get these following lines of error:

/opt/trame/activate_venv.sh: line 1: /deploy/server/venv/bin/activate: No such file or directory /opt/trame/run.sh: line 20: /deploy/server/launcher.json: No such file or directory Starting the wslink launcher at /usr/bin/python: Error while finding module specification for 'wslink.launcher' (ModuleNotFoundError: No module named 'wslink')

Is it because the environment variable for trame is not properly set? The only thing I removed from the shell scripts is the --gpu all, because i am running everythin on a virtual mashine and it seemed to cause some problems.

jourdain commented 1 month ago

My guess is that the venv did not get built or filled with your dependencies.

On Wed, Jul 10, 2024 at 10:30 Pierre-Louis Bonvin @.***> wrote:

I am trying to run the docker script that has been described in the docker folder. Instead of downloading paraview everytime I run the dockerfile, I have linked it to my local paraview binarie folder (ParaView-5.10.1-MPI-Linux-Python3.9-x86_64). The build seems to work great, as soon as the server image is run i get these following lines of error:

/opt/trame/activate_venv.sh: line 1: /deploy/server/venv/bin/activate: No such file or directory /opt/trame/run.sh: line 20: /deploy/server/launcher.json: No such file or directory Starting the wslink launcher at /usr/bin/python: Error while finding module specification for 'wslink.launcher' (ModuleNotFoundError: No module named 'wslink')

Is it because the environment variable for trame is not properly set? The only thing I removed from the shell scripts is the --gpu all, because i am running everythin on a virtual mashine and it seemed to cause some problems.

— Reply to this email directly, view it on GitHub https://github.com/Kitware/paraview-visualizer/issues/15, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACH45VLQUX7XVXR73O4GV3ZLT5JZAVCNFSM6AAAAABKUQCQISVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQYDAMRTGI3DGNA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

PierreLouis94 commented 1 month ago

Hi Sebastien,

Thank you for your prompt response.

I've been examining the provided Docker setup and it seems that there is no venv being built or am I missing something? Also the setup folder and it's content are not explicitly referenced or used in the scripts.

`` pierrelouisb@pierrelouis-vmwarevirtualplatform:~/paraview-visualizer/docker$ ./scripts/build_image.sh ~/paraview-visualizer/docker ~/paraview-visualizer/docker ~/paraview-visualizer/docker

As the error appears to happen before the dockerfile, I suppose the problem is somewhere in the build_server.sh. Is it possible that the image (kitware/trame:1.2-glvnd-runtime-ubuntu20.04-py39) could be the issue here?

jourdain commented 1 month ago

Those images are old. We should be using :py3.10-…