To support the case where your fully external application needs extra python modules, the default entrypoint of the paraviewweb image will look for a requirements.txt file in the directory and install those using: pip install -r "/pvw/requirements.txt" You can also mount other directories as needed, but this at least is required when running the paraviewweb container: docker run -v :/pvw. The second thing you must do for the above use case is mount “APP_DIR” as “/pvw” when you run the container. The rest of the directory structure is up to you. See the demo endpoints file for an example. That file should contain one mapping per line, where each line consists of an alias and a path, separated by a space. As another convenience, you can supply an endpoints.txt file in the directory with the mappings you want the internal apache server to set before starting. If requirements.txt is present, any modules it contains will be installed when the container is started. You also have the option to include a requirements.txt at the root of the directory structure, which can contain any extra python modules your application may need. The “APP_ROOT/See the demo launcher config for an example configuration file with those replacement values. You should first create a directory structure where your application lives (we’ll call it below) following this structure: / In order to run this image directly as a paraviewweb application, there are a few assumptions we make about the external directories as well as the locations of some key pieces. This section describes some of the internals which make that possible. We have created a separate repository as an example of a fully external demo web application application. The images built from this Dockerfile are designed to be used in one of two ways, either run directly with a fully external application (Fully external direct run For example: cd tools/docker/paraviewwebĭocker build -build-arg BASE_IMAGE=pv-v5.6.0-egl -t pvw-v5.6.0-egl. When you build this image, you can specify the base ParaView image to build on top of using the BASE_IMAGE build argument. The next layer in the stack builds on the ParaView layer and adds an apache webserver, along with setting up some infrastructure that supports ParaViewWeb applications in general. You could also change v5.6.0 in the command above to master to build against the master versions, or change ‘egl’ to ‘osmesa’ to build with software rendering, for example. For example, to build against a tagged version like v5.6.0, the commands might look like: cd /Scripts/docker/ubuntuĭocker build -build-arg PARAVIEW_TAG=v5.6.0 -build-arg SUPERBUILD_TAG=v5.6.0 -RENDERING="egl" -t pv-v5.6.0-egl. ![]() To achieve this, use the build arguments PARAVIEW_TAG and SUPERBUILD_TAG. ![]() The Dockerfile used to build these images allows you to specify the version of ParaView and the ParaViewSuperbuild you wish to use when building the container. In all of these images, ParaView is installed at /opt/paraview. The OSMesa builds are useful when no such graphics card and driver are available, and in that case you will have the choice of using llvm or swr backends at runtime. ![]() ![]() The EGL builds are useful for deployment on machines with NVidia graphics cards supporting driver version 384 or later. The Dockerfile for building these containers is located in the ParaView-Superbuild repository, and it supports two basic configurations, EGL and OSMesa. The stack of containers looks like the picture below: Layer One - ParaViewĪt the bottom of the stack we need to start with a container which has ParaView installed. This document aims to describe that container hierarchy, and how you can make use of the images. Additionally, there are a couple layers of Dockerfiles in this repository that can build upon the resulting ParaView containers to support ParaViewWeb applications. In the ParaView-Superbuild repository we have a Dockerfile for building various configurations of ParaView.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |