Docker for hosting Virtuoso.
The Virtuoso is built from a specific commit SHA in https://github.com/openlink/virtuoso-opensource.
The Docker image tags include the Virtuoso version installed in the container. The following versions are currently available:
- 1.3.2-virtuoso7.2.5 (or virtuoso7.2.5 for latest)
- 1.3.2-virtuoso7.2.4 (or virtuoso7.2.4 for latest)
- 1.3.2-virtuoso7.2.2 (or virtuoso7.2.2 for latest)
- 1.3.2-virtuoso7.2.1 (or virtuoso7.2.1 for latest)
- 1.3.2-virtuoso7.2.0 (or virtuoso7.2.0 for latest)
docker run --name my-virtuoso \
-p 8890:8890 -p 1111:1111 \
-e DBA_PASSWORD=myDbaPassword \
-e SPARQL_UPDATE=true \
-e DEFAULT_GRAPH=http://www.example.com/my-graph \
-v /my/path/to/the/virtuoso/db:/data \
-d tenforce/virtuoso
The Virtuoso database folder is mounted in /data.
The Docker image exposes port 8890 and 1111.
The image can also be configured and used via docker-compose.
db:
image: tenforce/virtuoso:1.3.1-virtuoso7.2.2
environment:
SPARQL_UPDATE: "true"
DEFAULT_GRAPH: "http://www.example.com/my-graph"
volumes:
- ./data/virtuoso:/data
ports:
- "8890:8890"
The dba password can be set at container start up via the DBA_PASSWORD environment variable. If not set, the default dba password will be used.
The SPARQL_UPDATE permission on the SPARQL endpoint can be granted by setting the SPARQL_UPDATE environment variable to true.
All properties defined in virtuoso.ini can be configured via the environment variables. The environment variable should be prefixed with VIRT_ and have a format like VIRT_$SECTION_$KEY. $SECTION and $KEY are case sensitive. They should be CamelCased as in virtuoso.ini. E.g. property ErrorLogFile in the Database section should be configured as VIRT_Database_ErrorLogFile=error.log.
Enter the Virtuoso docker, open ISQL and execute the dump_nquads procedure. The dump will be available in /my/path/to/the/virtuoso/db/dumps.
docker exec -it my-virtuoso bash
isql-v -U dba -P $DBA_PASSWORD
SQL> dump_nquads ('dumps', 1, 10000000, 1);
For more information, see http://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/VirtRDFDumpNQuad
Make the quad .nq files available in /my/path/to/the/virtuoso/db/dumps. The quad files might be compressed. Enter the Virtuoso docker, open ISQL, register and run the load.
docker exec -it my-virtuoso bash
isql-v -U dba -P $DBA_PASSWORD
SQL> ld_dir('dumps', '*.nq', 'http://foo.bar');
SQL> rdf_loader_run();
Validate the ll_state of the load. If ll_state is 2, the load completed.
select * from DB.DBA.load_list;
For more information, see http://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/VirtBulkRDFLoader
By default, any data that is put in the toLoad directory in the Virtuoso database folder (/my/path/to/the/virtuoso/db/toLoad) is automatically loaded into Virtuoso on the first startup of the Docker container. The default graph is set by the DEFAULT_GRAPH environment variable, which defaults to http://localhost:8890/DAV.
A virtuoso backup can be created by executing the appropriate commands via the ISQL interface.
docker exec -i virtuoso_container mkdir -p backups
docker exec -i virtuoso_container isql-v <<EOF
exec('checkpoint');
backup_context_clear();
backup_online('backup_',30000,0,vector('backups'));
exit;
To restore a backup, stop the running container and restore the database using a new container.
docker run --rm -it -v path-to-your-database:/data tenforce/virtuoso virtuoso-t +restore-backup backups/backup_ +configfile /data/virtuoso.ini
The new container will exit once the backup has been restored, you can then restart the original db container.
It is also possible to restore a backup placed in /data/backups using a environment variable. Using this approach the backup is loaded automatically on startup and it is not required to run a separate container.
docker run --name my-virtuoso \
-p 8890:8890 \
-p 1111:1111 \
-e DBA_PASSWORD=dba \
-e SPARQL_UPDATE=true \
-e BACKUP_PREFIX=backup_ \_
-v path-to-your-database:/data \
-d tenforce/virtuoso
Contributions to this repository are welcome, please create a pull request on the master branch.
New features will be tested on tenforce/virtuoso:latest first. Once the image is verified, version branches will be rebased on master.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent