ModuleNotFoundError: No module named 'wslink'

[PierreLouis94]

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]

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 <#15>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACH45VLQUX7XVXR73O4GV3ZLT5JZAVCNFSM6AAAAABKUQCQISVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQYDAMRTGI3DGNA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[PierreLouis94]

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

• Restarting Apache httpd web server apache2
  AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.2. Set the 'ServerName' directive globally to suppress this message
  ...done.
  Starting server...
  /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')
  [+] Building 0.3s (9/9) FINISHED docker:default
  => [internal] load build definition from Dockerfile 0.1s
  => => transferring dockerfile: 682B 0.0s
  => [internal] load metadata for docker.io/kitware/trame:1.2-glvnd-runtime-ubuntu20.04-py39 0.0s
  => [internal] load .dockerignore 0.0s
  => => transferring context: 2B 0.0s
  => [1/4] FROM docker.io/kitware/trame:1.2-glvnd-runtime-ubuntu20.04-py39 0.0s
  => [internal] load build context 0.0s
  => => transferring context: 258B 0.0s
  => CACHED [2/4] RUN install -d -o trame-user -g trame-user /deploy 0.0s
  => CACHED [3/4] RUN mkdir -p /opt/paraview && cd /opt/paraview && wget -qO- https://www.paraview.org/files/v5.10/ParaView- 0.0s
  => CACHED [4/4] COPY --chown=trame-user:trame-user ./server /deploy/server 0.0s
  => exporting to image 0.0s
  => => exporting layers 0.0s
  => => writing image sha256:02abf68b1418960fff0373b2ecf1ba70e99bc0a0d3483c4410e73ed546ed9e7a 0.0s
  => => naming to docker.io/library/pv-visualizer 0.0s
  /home/pierrelouisb/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]

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