atomgraph / fuseki-docker

Docker image for Apache Jena's Fuseki SPARQL endpoint

fuseki-docker

Docker image for Apache Jena's Fuseki (v2) triplestore server

Endpoints

In the following examples which use /ds as the dataset path, these main endpoints are available:

• http://localhost:3030/ds/sparql for SPARQL Query
• http://localhost:3030/ds/update for SPARQL Update
• http://localhost:3030/ds/data for Graph Store (read-write)
• http://localhost:3030/ds/get for Graph Store (read-only)

They can be redefined in configuration.

Post 3030 has to be mapped to be able to access it on the Docker host.

Usage

Arguments after the image name (atomgraph/fuseki) become arguments to the Fuseki server (no UI). As the name explains, this server version does not include the user interface.

Examples

Empty memory dataset:

docker run --rm -p 3030:3030 atomgraph/fuseki --mem /ds

Dataset from file data.nt (which is mounted as part of the current directory):

docker run --rm -p 3030:3030 -v $(pwd):/usr/share/data atomgraph/fuseki --file=/usr/share/data/data.nt /ds

Help (all run options explained):

docker run --rm atomgraph/fuseki --help

Profiling

Use Dockerfile.profiler to build the image instead of the default Dockerfile.

Then append the following settings to the JAVA_OPTIONS env variable:

-Dcom.sun.management.jmxremote=true \
-Djava.rmi.server.hostname=127.0.0.1 \
-Dcom.sun.management.jmxremote.host=0.0.0.0 \
-Dcom.sun.management.jmxremote.port=9991 \
-Dcom.sun.management.jmxremote.rmi.port=9991 \
-Dcom.sun.management.jmxremote.ssl=false \
-Dcom.sun.management.jmxremote.registry.ssl=false \
-Dcom.sun.management.jmxremote.authenticate=false \
-Djava.net.preferIPv4Stack=true

and use VisualVM to create a JMX connection to 127.0.0.1:9991. Only tested with VisualVM running on Windows 10 and the remote Fuseki app running in a Docker container on WSL2.

fuseki-docker's Issues

Add semver tags to docker hub builds?

Would be nice to have tags for the builds that correspond to fuseki version, including tag for latest major release, e.g., atomgraph/fuseki:3.14 and atomgraph/fuseki:3.

Providing a dataset to the fuseki instance

I managed to build a fuseki container from your Dockerfile, but it seems you need to provide a dataset when running docker run. Does this need to be a TDB? Can the dataset be provided as a command line argument or should it be specified by modifying the Dockerfile?

Temporary server fails on Ubuntu (fuseki-tdb branch)

As reported in AtomGraph/LinkedDataHub#27:

Creating linkeddatahub_email-server_1 ...
Creating linkeddatahub_nginx_1 ...
Creating linkeddatahub_fuseki-end-user_1 ...
Creating linkeddatahub_linkeddatahub_1 ...
Creating linkeddatahub_email-server_1
Creating linkeddatahub_fuseki-admin_1 ...
Creating linkeddatahub_nginx_1
Creating linkeddatahub_fuseki-end-user_1
Creating linkeddatahub_linkeddatahub_1
Creating linkeddatahub_nginx_1 ... done
Attaching to linkeddatahub_email-server_1, linkeddatahub_fuseki-admin_1, linkeddatahub_linkeddatahub_1, linkeddatahub_fuseki-end-user_1, linkeddatahub_nginx_1
email-server_1     | + sed -ri '
email-server_1     |    s/^#?(dc_local_interfaces)=.*/\1='\''[0.0.0.0]:25 ; [::0]:25'\''/;
email-server_1     |    s/^#?(dc_other_hostnames)=.*/\1='\'''\''/;
email-server_1     |    s/^#?(dc_relay_nets)=.*/\1='\''172.23.0.4\/16'\''/;
email-server_1     |    s/^#?(dc_eximconfig_configtype)=.*/\1='\''internet'\''/;
email-server_1     | ' /etc/exim4/update-exim4.conf.conf
email-server_1     | + update-exim4.conf -v
email-server_1     | using non-split configuration scheme from /etc/exim4/exim4.conf.template
email-server_1     |     1 LOG: MAIN
email-server_1     |     1   exim 4.92 daemon started: pid=1, -q15m, listening for SMTP on port 25 (IPv4)
fuseki-admin_1     | Starting temporary server
fuseki-admin_1     | Temporary server started.
linkeddatahub_1    | ### Generating server certificate
fuseki-end-user_1  | Starting temporary server
fuseki-end-user_1  | Temporary server started.
nginx_1            | ### Waiting for linkeddatahub...
nginx_1            | ### linkeddatahub responded
fuseki-admin_1     | http://localhost:3333/ds/ not responding, exiting...
linkeddatahub_fuseki-admin_1 exited with code 1
fuseki-end-user_1  | http://localhost:3333/ds/ not responding, exiting...
linkeddatahub_fuseki-end-user_1 exited with code 1
linkeddatahub_1    |
linkeddatahub_1    | ### Quad store URL of the root admin service: http://fuseki-admin:3030/ds/
linkeddatahub_1    |
linkeddatahub_1    | ### Secretary's WebID URI: https://localhost:4443/admin/acl/agents/e413f97b-15ee-47ea-ba65-4479aa7f1f9e/#this
linkeddatahub_1    |
linkeddatahub_1    | ### Secretary WebID certificate's DName attributes: CN=LinkedDataHub,OU=LinkedDataHub,O=AtomGraph,L=Copenhagen,ST=Denmark,C=DK
linkeddatahub_1    |
linkeddatahub_1    | ### Secretary WebID certificate's modulus: c33d3ab2873ed78...
linkeddatahub_1    | ### Waiting for http://fuseki-admin:3030/ds/...
linkeddatahub_1    | ### URL http://fuseki-admin:3030/ds/ not responding after 20 seconds, exiting...
linkeddatahub_linkeddatahub_1 exited with code 

Base image on linked-solutions/fuseki-base

linked-solutions/fuseki-base is meant to provide a base image for various fuseki docker distributions. It uses maven so can be always use the latest fuseki version, see https://github.com/linked-solutions/fuseki-base.