Skip to content

sincedb_path handling #10

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

Closed
pazoozooCH opened this issue Apr 3, 2015 · 2 comments
Closed

sincedb_path handling #10

pazoozooCH opened this issue Apr 3, 2015 · 2 comments

Comments

@pazoozooCH
Copy link

I've noticed some problems with the sincedb handling for file parsing: By default, Logstash will try to store it's sincedb-file in the $HOME directory. In this image, this will be evaluated to /root, but Logstash runs as user logstash and will not have permissions to save in this folder.

Another problem is that the sincedb file will be lost if the container is removed (e.g. with a version update). Obviously, this can be solved using volume mounting or a data container. Maybe it would be possible to change the $HOME directory for the logstash user and declare it as a volume in the Dockerfile at the same time?

@yosifkit
Copy link
Member

So, $HOME should be working correctly since #12. Would something like docker-library/elasticsearch#77 be helpful to allow you to specify any non-root user and group to run as, using the --user flag on docker run?

@tianon
Copy link
Member

tianon commented Aug 22, 2016

Given that #11 is tracking the ability to run as a different user easily and that the HOME issue described here is fixed, I'm closing this one. 👍

@tianon tianon closed this as completed Aug 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants