Paraview web inside docker container

rasunag27 · October 7, 2021, 8:22am

Hi,

I am trying to work on Paraview web inside docker container. For this, I dint use the default BASE_IMAGE=kitware/paraviewweb:pv-v5.6.0-egl, but instead I have my own image in which Paraview web required files are loaded.

I have used same settings for apache2 and launcher file inside docker container as tested outside without docker.
When I run start.sh and apache2 inside docker container, I get connection error in the link http://localhost/lite/?data=/dir , and the error and proxy files are empty.
The ProxyPass in apache2 is set as ProxyPass /paraview http://localhost:8080/paraview.

How do I run the correctly in detached mode, so as to load paraview web correctly in the URL.

Regards,
Sunag R A.

jourdain · October 7, 2021, 2:22pm

Why don’t you use the standard pvw docker and configure the launcher to run your ParaView Lite rather than the one inside the bundled paraview? The image is designed to run any pvw app and therefore, your code should not differ in that regard.

Also you will need to provide error messages/logs so we could have an idea where the issue is coming from.

Since you are using the EGL version do you have all your nvidia runtime working as expected?

rasunag27 · October 7, 2021, 3:14pm

Hi,

No, I am not using EGL version. I mentioned that to show that I am not using any version provided by kitware.
The process of working in my docker container is this:

a. Dockerfile with all the installation along with apache2. Copy data directory which contains (pvw, proxy, pv, conf, logs etc). The pv version I am using is pv-5.9.0.
b. The configuration of apache2 and launcher file is done before building image.

Here is the apache2 configuration which contains the log path.

  <VirtualHost *:80>
      #ServerName   localhost
      ServerAdmin  sunag.ra@123.com
      DocumentRoot /home/data/www

      ErrorLog /home/data/logs/apache_error.log
      CustomLog /home/data/logs/apache_access.log combined

      <Directory /home/data/www/>
          Options Indexes FollowSymLinks
          Order allow,deny
          Allow from all
          AllowOverride None
          Require all granted
      </Directory>

      # Handle launcher forwarding
      ProxyPass /paraview http://localhost:9000/paraview

      # Handle WebSocket forwarding
      RewriteEngine On
      RewriteMap session-to-port txt:/home/data/proxy.txt
      RewriteCond %{QUERY_STRING} ^sessionId=(.*)&path=(.*)$ [NC]
      RewriteRule ^/proxy.*$  ws://${session-to-port:%1}/%2  [P]
    </VirtualHost>

Now,

I need to run the image with start.sh so that launcher will run and apache2 with port so that pvw will run. What should be the command line for docker run?

Does my need make understandable?

Regards,

Sunag R A.

Drew_Lazzeri · October 7, 2021, 7:27pm

Hi Sunag,

Is this what you are looking for?

We built those images to support many use cases, and therefore we’d like to know what we’ve forgotten. Can you explain your motivation for building your own?

rasunag27 · October 8, 2021, 4:29am

Hi Drew,

Yes, this is something this I am trying to run from docker.

I am trying to use single image where OpenFOAM simulations are run and the obtained vtk files are stored in the pvw directory. So, Dockerfile contains OpenFOAM related installation and all the config files for pvw.
I am trying to understand how this command should be implemented (along with any changes to do for apache2 config) for the docker image so as to run pvw.
Or, should I need to create separate Dockerfile and build all together separate image?

sudo docker run --gpus all                 \
    -p 0.0.0.0:9000:80                      \
    -v ~:/data                               \
    -e "SERVER_NAME=localhost:9000"           \
    -e "PROTOCOL=ws"                           \
    -ti kitware/paraviewweb:pvw-egl-demo-v5.6.0

Regards,
Sunag R A.

Drew_Lazzeri · October 8, 2021, 9:14pm

Hi Sunag,

I think the simplest path forward would be to use two images, docker’s storage support to transfer the files between them. One image would be your OpenFOAM simulation, specifying to keep the vtk files outside of docker after it runs. The other would be our provided paraview web image, which will have access to the vtk files with the -v volume in the docker run command

sudo docker run --gpus all                 \
    -p 0.0.0.0:9000:80                      \
    -v ~:/data                               \
    -e "SERVER_NAME=localhost:9000"           \
    -e "PROTOCOL=ws"                           \
    -ti kitware/paraviewweb:pvw-egl-demo-v5.6.0

rasunag27 · October 26, 2021, 7:13am

Hi Drew,
Based on your suggestion, I have made two docker images, one which gets me the vtk file and other for visualization.

But for visualization, I have done the following process.

a. Copied pv-5.9.0 and pvw contents which relates to launcher and start.sh file to docker container.
b. Run apache2 along with start.sh file
c. Run the docker with exposing network port to 80 as docker run -p 8080:80.
d. The path is working good with http://localhost/lite/?data=/dir, but when I click connect to paraview, I get error stating
Session did not start before timeout expired. Check session logs.

I checked with error log in pvw/logs, where an error mentioned as Segmentation fault with Loguru expection occurance.

I went through this issue loguru issue and found that the vtkXOpenGL doesn’t work in cloud.

I tried working with Osmesa 5.9.0 version. The log file shows:

wslink: Starting factory
CRITICAL:twisted:wslink: Starting factory

Now also, I am getting the same error.

Any work around needs to be done?

Regards,
Sunag R A.

Drew_Lazzeri · October 31, 2021, 12:08am

Hi Sunag,

My suggestion may not have been clear enough. I suggest that you use two docker images, and that for the paraview image you use our images available here:
https://hub.docker.com/r/kitware/paraviewweb. These are how the examples run in the documentation here
https://kitware.github.io/paraviewweb/docs/docker.html

rasunag27 · November 2, 2021, 11:04am

Hi Drew,

So I tried with docker image itself. I wanted to work without gpu and hence I worked by pulling the “osmesa” version by using the command

docker pull kitware/paraviewweb:pvw-v5.6.0-osmesa

But when I run the command with docker run command, I get the following error:

cp: cannot stat '/pvw/launcher/config.json': No such file or directory
Backing up /etc/apache2/sites-available/001-pvw.conf to /etc/apache2/sites-available/001-pvw.conf.BAK
/opt/paraviewweb/scripts/start.sh: line 64: /opt/launcher/config-template.json: No such file or directory
Starting/Restarting Apache webserver
 * Restarting Apache httpd web server apache2                                                                                                                          AH00112: Warning: DocumentRoot [/pvw/www] does not exist
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.3. Set the 'ServerName' directive globally to suppress this message
                                                                                                                                                                [ OK ]
Starting the wslink launcher
ERROR: Unable to read config file.
No JSON object could be decoded
<traceback object at 0x7f1298231098>

And follows up with the template of launcher json file.

I did try pulling “egl” version using docker pull again. When I ran the image, it ran correctly and the webpage is opening at http://localhost:9000/lite/. Since, gpu is not involved, when I click “connect to paraview”, it throws an error in the logfile.

So, is there any other version of “osmesa” image which runs completely? I tried with 5.6 and 5.7.

Regards,
Sunag R A.

jourdain · November 3, 2021, 2:29pm

The answer to your question is provided in the last comment of that issue