[
https://issues.apache.org/jira/browse/JENA-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17223170#comment-17223170
]
Martin Kopeček edited comment on JENA-1949 at 10/29/20, 7:39 PM:
-----------------------------------------------------------------
Sorry, I wanted to write the package, but I couldn't find it and decided to
fill it in later. You were faster :)
The package that I added to *--add-modules* was *jdk.crypto.cryptoki*. That
solved the problem.
The error was the following:
!image-2020-10-29-20-32-25-174.png!
When I went inside the container, I could run wget on the URL of the context
file fine. Then using riotcmd.riot from the fuseki-server.jar on the same URL I
got:
!image-2020-10-29-20-36-15-499.png!
With the volume no error, just that when it is declared as anonymous volume it
doesn't show in the container size and it was then hard to find that its
actually Fuseki taking up the 33GB of space (as a result of the evergrowing
TBD2 and lot of updates).
was (Author: smallhillcz):
Sorry, I wanted to write the package, but I couldn't find it and decided to
fill it in later. You were faster :)
The package that I added to *--add-modules* was *jdk.crypto.cryptoki*. That
solved the problem.
The error was the following:
!image-2020-10-29-20-32-25-174.png!
When I went inside the container, I could run wget on the URL of the context
file fine. Then using riotcmd.riot from the fuseki-server.jar on the same URL I
got:
!image-2020-10-29-20-36-15-499.png!
> Docker build tools for Fuseki
> -----------------------------
>
> Key: JENA-1949
> URL: https://issues.apache.org/jira/browse/JENA-1949
> Project: Apache Jena
> Issue Type: New Feature
> Components: Fuseki
> Affects Versions: Jena 3.16.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Major
> Fix For: Jena 3.17.0
>
> Attachments: image-2020-10-29-20-32-25-174.png,
> image-2020-10-29-20-33-20-634.png, image-2020-10-29-20-36-15-499.png
>
> Time Spent: 6h 10m
> Remaining Estimate: 0h
>
> JENA-909 is for a docker container available in docker hub.
> Integrating complete deployment within the project release process is
> difficult because we do not want docker container binary artifact going to
> Docker Hub until (1) they are not snapshots and (2) the vote has concluded
> successfully.
> At the same time, being stateful, a deployment needs to consider where
> databases and logs go outside the container.
> This ticket is for the setup and scripts to build an image, not to publish it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
