[
https://issues.apache.org/jira/browse/JENA-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388712#comment-14388712
]
Stian Soiland-Reyes commented on JENA-909:
------------------------------------------
I have already done this - but did not submit it as a pull request as I didn't
get much feedback here (but good feedback on the docker hub).
https://registry.hub.docker.com/u/stain/jena-fuseki/
https://github.com/stain/jena/tree/fuseki2-docker/jena-fuseki2/jena-fuseki-docker
If this goes in, should we then ask for a 'jena' user at
registry.hub.docker.com to make it official?
How does it align with release process? The Docker way to do it is to link to a
GitHub repository and have it build based on tags or pushes - but we don't have
access to http://github.com/apache/jena/ ourselves to approve such a link.
Or we can just do it manually after each Fuseki release - I'm OK to do that, as
I've been doing so far :)
(There's also a Maven docker plugin which could do it as part of the release,
but that would require Docker installed and given permissions on the machine
doing the release)
> Create Docker launcher for Fuseki
> ---------------------------------
>
> Key: JENA-909
> URL: https://issues.apache.org/jira/browse/JENA-909
> Project: Apache Jena
> Issue Type: Improvement
> Components: Fuseki
> Reporter: Andy Seaborne
>
> Provide a Docker launcher and setup documentation for Fuseki2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
