This project creates three dockerized containers,
vivoThe vivo instancesolrA standalone solr instance, based on a solr docker imagemariadbA standalone mariadb instance.
These images can be used together, or independently to setup some development or working VIVO docker instances.
Regardless of the usage, you will need to build the images, which require the following steps:
docker-compose up -dThe example docker-compose.yml is a typical installation for trying out a simple VIVO installation in docker. This file starts three containers and uses the standard SDB system with the mariadb backend. This example also shows how a local directory example-config is used to overwrite the default runtime.properties as installed by the Dockerfile. Here the root password, and the domain are modified.
docker-compose up -dWill start this project. Navigating to http://localhost:8080/vivo will then start this simple instance.
If you get an error indicating that the database was not found, this could be due to a bug where the vivo instance is not waiting on the mariadb instance to initialize. IF you have this error, try docker-compose down; docker-compose up -d.
You can use these same containers to develop a local VIVO installation. In this
case, your docker-compose.yml file would only contain the solr and the
mariadb images. You can then connect to these images with your local setup.
- Install VIVO as usual, with the following changes to
runtime.properties:vitro.local.solr.url = http://localhost:8983/solr/vivocore - Open a browser to: http://localhost:8080/vivo
Currently, the Mariadb Dockerfile includes SQL, that initializes a username:password for VIVO to communicate with mariadb. If you'd like to change this, you'll need to perform some additional sql grant commands to alter this.
For earlier Dockerized VIVO releases, see vivo-docker