You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
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?
The text was updated successfully, but these errors were encountered: