feelpp/docker

Containers for Feel++

Guillaume Dollé

@gdolle

I guess in newer version opengl2 is by default

Christophe Prud'homme

@prudhomm

what do you mean ?

why is opengl involved ?

ah ok renderingbackend.opengl2

Guillaume Dollé

@gdolle

yes!

Christophe Prud'homme

@prudhomm

is there a quick fix ?

Guillaume Dollé

@gdolle

I think with @vincentchabannes that's could be the problem

but we have still to check

Guillaume Dollé

@gdolle

@prudhomm for the pvserver problem, recompiling with
-DVTK_RENDERING_BACKEND=OpenGL2
solve the problem (I tested on atlas).

PS: Binary version of paraview use opengl2 vtk backend by default.

This message was deleted

Guillaume Dollé

@gdolle

Can you rerun the docker build chain ?

Christophe Prud'homme

@prudhomm

ok thx

Christophe Prud'homme

@prudhomm

@/all develop and master Feel++ docker images have been rebuilt to fix the pvserver issue mentionned by @gdolle/. Do you confirm that it is ok now @gdolle ?

Guillaume Dollé

@gdolle

This message was deleted

Guillaume Dollé

@gdolle

@prudhomm I think the image has not been regenerated/pushed on dockerhub.
Docker pull did not download upadtes.

(I still redownload the image, but paraview.5.1.renderingbackend.opengl did not changed.
Maybe it has not been pushed ?

Christophe Prud'homme

@prudhomm

@gdolle here is what I have from paraview compilation:

-- Backend OpenGL2 modules: vtkDomainsChemistryOpenGL2;vtkIOExportOpenGL2;vtkImagingOpenGL2;vtkRenderingContextOpenGL2;vtkRenderingGL2PSOpenGL2;vtkRenderingLICOpenGL2;vtkRenderingOculus;vtkRenderingOpenGL2;vtkRenderingOpenVR;vtkRenderingVolumeOpenGL2
-- Enabling modules for OpenGL2.

I will further check but new images have been uploaded (look at hub.docker.com for example)

Guillaume Dollé

@gdolle

hum.. Where is install paraview ? System wide /usr/ ?

Christophe Prud'homme

@prudhomm

/usr/local

Guillaume Dollé

@gdolle

the tag is latest ?

Christophe Prud'homme

@prudhomm

yes or ubuntu-16.10

feelpp/feelpp-env

Guillaume Dollé

@gdolle

@vincentchabannes just told me that changes in develop have not been taken into account

I'll try 16.10

Vincent Chabannes

@vincentchabannes

@prudhomm I just tried with tag feelpp/feelpp-libs:ubuntu-16.10 and it’s seems that is a very old version of feel++

Vincent Chabannes

@vincentchabannes

ok, I think understand the problem. All is good with develop-ubuntu-16.10. but not for latest tag. Probably this one is linked to ubuntu-17.10 but ubuntu-17.10 is not updated at this time, no?

Guillaume Dollé

@gdolle

Ok pvserver works on feelpp/feelpp-toolboxes:develop-ubuntu-16.10

I'll add a doc in the book

Christophe Prud'homme

@prudhomm

ah yes that’s it ;)

I will move the latest tag

Guillaume Dollé

@gdolle

ok. Then I'll see with @Trophime for the hifimagnet part.

Guillaume Dollé

@gdolle

We tested with @vincentchabannes multi clients connection on the same pvserver via the container. Works well!

Guillaume Dollé

@gdolle

pvserver+Insitu ok on the docker image.

Guillaume Dollé

@gdolle

@prudhomm I just tested also with singularity, works perfectly too. insitu on atlas with fsi toolbox :+1:

Guillaume Dollé

@gdolle

For those who want to test with singularity:

module load singularity/2.2.1

then run the image that I provide

singularity shell -c -B ${HOME}/feel:/feel  /data/images/singularity_feelpp-toolboxes-develop-ubuntu-16.10.img

then

pvserver &

Here in Paraview connect to the pvserver with paraview, then connect to catalyst (port 22222 is default), pause catalyst,

mpirun -np 8 feelpp_toolboxes_fsi_2d --config-file Testcases/FSI/wavepressure2d/wavepressure2d.cfg --exporter.format=vtk --exporter.vtk.insitu.enable=1

An object will appears in paraview.
Set the object in the browser visible by clicking on the eye icon.
Put the filter "warp by vector" and set the propertie scale to 15.
Resume catalyst. And enjoy ! :)

Christophe Prud'homme

@prudhomm

@/all I relaunched the docker images build to move back the latest and stable tags to develop-ubuntu-16.10 and master-ubuntu-16.10 respectively

they should be ready in about an hour or so

Trophime

@Trophime

@prudhomm I've uploaded images for Salome and Hifimagnet. Dcokerhub reports some vulnerabilies issues when scanning the images. Do you have an idea how to fix this?

Christophe Prud'homme

@prudhomm

are they built automatically or do you do that by hand ?

Trophime

@Trophime

both are build with a script

Christophe Prud'homme

@prudhomm

sure but you execute the script yourself right ?

Trophime

@Trophime

see in docker/hifimagnet /build_hifimanget.sh and docker/salome/build_salome.sh

yes unfortunatly :(

Trophime

@Trophime

I'll need you help to automate all that but I have to fix issue with "make install" in hifimagnet first ;)

By the way I'll manage to package feelpp and feelpp-toolbox-solid. Cannot package all the toolboxes at once: it requires two much disk space!

Guillaume Dollé

@gdolle

/@all For info, singularity 2.3 should be released this wednesday 05/01/2017 with some nice features.
We should be able to use nvidia driver directly with -n option.
Also, sudo should not be required anymore for creating images/bootstrap :+1:

victorsndvg

@victorsndvg

Thanks @gdolle :+1 !

Both are great improvements in singularity usage.
I've read that cuda compatibility is very tricky with release 2.1. We will explore this version ASAP

Guillaume Dollé

@gdolle

For information. To launch X11 apps with graphic acceleration via singularity, do not use the option -c otherwise it does not share x11 env and you'll get an error like

No protocol specified
paraview: cannot connect to X server :0

Where communities thrive

People

Repo info

Activity