k0105
commented
8 years ago ############################
## Freebase Service Image ##
############################
# Proposed image name: freebase
# Readme https://github.com/brmson/yodaqa/tree/master/data/freebase
# Inherit official Java image, see https://hub.docker.com/_/java/
FROM java:8
# Copy fuseki files
ADD ./jena-fuseki-1.1.1 /jena-fuseki-1.1.1
# Same as "export TERM=dumb"; prevents error "Could not open terminal for stdout: $TERM not set"
ENV TERM dumb
# Define working directory
WORKDIR /jena-fuseki-1.1.1
# Expose port
EXPOSE 3030
##########
# BEWARE #####################################################################################
# With SELinux you need to run chcon -Rt svirt_sandbox_file_t /run/media/<user>/<longid>/home/<user>/Downloads/Backends/jena-fuseki-1.1.1/d-freebase/
##############################################################################################
# Can be built with: "docker build -t freebase ."
# docker run -it -v /run/media/<user>/<longid>/home/<user>/Downloads/Backends/jena-fuseki-1.1.1/d-freebase/:/jena-fuseki-1.1.1/d-freebase/ --entrypoint="./fuseki-server" -p 3030:3030 freebase --loc d-freebase /freebase
# RUN ./fuseki-server --loc d-freebase /freebase is done in run command; need to map as volume (read-only via :ro)
pasky
So far I have only provided one Dockerfile for Yoda itself, which is nice and all, but containerization only really makes sense if we put all backends in containers, because then we can freely distribute and orchestrate them. However, for this we need to map huge DBs via volumes (which also requires adding according SELinux rules on systems that use it). I have done this for the label services. Based on this Dockerfile it should be straightforward to put any backend into a container. Here goes:
I will add more Dockerfiles as soon as I find the time and show how to orchestrate them, but for now this example should already demonstrate all tricks that were still needed to accomplish the task.
Best wishes, Joe