-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
issue when using a volume for data #35
Comments
Hi,
and the issue appeared:
It appears that Jena server is not shutting down gracefully. Update: Just noticed this solution and it seems to work. |
Thanks, I am able to reproduce. In a sense there are two issues:
The entrypoint currently also does the optional loading after server is started, which is why the |
Thanks for your explanation! Is there a way for hook into this proces with the |
You can save the PID from We tried a similar approach but abandoned it due to the complexity: |
This is the same issue as #41 I fixed it by creating my own DockerFIle which install procps and now when I stop my container lock files are removed :
There is a PR waiting merge : #40 |
@stain FYI this issue can be closed. |
Workaround stain/jena-docker#35
Hi,
I have an issue with the jena-fuseki docker image.
I have the following configuration in my docker-compose file:
When I start this container for the first time, it works without any issues. When I stop the container and start it for a second time, I get the following errors in the log:
the problem seems to be the file /fuseki/system/tdb.lock. Whenever this file is present, the above error is triggered. When I remove the file, the container starts normally again.
it seems to me that on shutdown of the container, this file should be cleaned up.
Is there any fix or workaround for this issue?
The text was updated successfully, but these errors were encountered: