datavirtuality-docker

This repository includes all needed configuration and scripts to run Data Virtuality Server as a Docker container.

⚠️ This is a technology preview: It is not yet recommended to be used in productive setups!

How to build this image

Prerequisites

• Before being able to build the image, you will the Data Virtuality Server Linux ZIP archive. Please ask your technical Data Virtuality contact on how to retrieve it.
• A separate PostgreSQL database server is required to host the configuration database. This can be either a separate Docker container or a conventional server.

Build the image

Run the provided script to build the image, passing the name and version of the image, as well as the Data Virtuality Server Linux ZIP archive:

$ ./dvserver-build.sh dvserver 2.3.10 dvserver-RELEASE_2.3.10.linux.x86_64.zip

How to use this image

Before starting the image, open the file config.env and provide the credentials on how to connect to the PostgreSQL configuration database.

Start a Data Virtuality Server container

Starting a container is simple, a bash script is included in the repository:

$ ./dvserver-run.sh dvserver 2.3.10

Persistent data

By default, all data created during the runtime of the container remains within the container (except for the configuration database). To persist the data, you can either use a volume or bind mount. Volumes are recommended by Docker as the preferred way. The following files/folders are stored inside the volume:

• log: Directory containing all application log files
• license.lic: The Data Virtuality license file
• dvserver-standalone.xml: A central configuration file that usually does not need to be edited by the user directly

Using a volume

Pass a volume as --volume $volume_name:/opt/datavirtuality/persistent_data.

The dvserver-run.sh script has this mechanism already built-in and you can pass the name of the volume to be used as a second parameter. The volume will be created automatically if it doesn't exist yet:

$ ./dvserver-run.sh dvserver 2.3.10 dv_data

Using a bind mount

If you need to use a bind mount, you can pass the option as --mount type=bind,source=/tmp/source_directory,target=/opt/datavirtuality/persistent_data. Replace /tmp/source_directory with an existing path on the host.

docker-compose

You can also use docker compose to manage the Data Virtuality Server container and the PostgreSQL configuration database container. See dvserver-compose.yml for an example configuration that can be started with docker-compose -f dvserver-compose.yml up.