Allow Elasticsearch 5 container to run as configurable user #46
Comments
orangejulius
added a commit
that referenced
this issue
Jan 16, 2019
This sets some more permissive permissions on various directories, files, and executables used in the Elasticsearch 5 docker image. It allows the user the container processes run under to be changed from the default of 1000, which helps keep things consistent with the rest of the Pelias containers. Fixes #46
orangejulius
added a commit
that referenced
this issue
Jan 17, 2019
This sets some more permissive permissions on various directories, files, and executables used in the Elasticsearch 5 docker image. It allows the user the container processes run under to be changed from the default of 1000, which helps keep things consistent with the rest of the Pelias containers. Fixes #46
calpb
pushed a commit
to sorelle/docker
that referenced
this issue
Mar 29, 2021
This sets some more permissive permissions on various directories, files, and executables used in the Elasticsearch 5 docker image. It allows the user the container processes run under to be changed from the default of 1000, which helps keep things consistent with the rest of the Pelias containers. Fixes pelias#46
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now, the pelias/elasticsearch:5.6.12 image does not support running as a user other than
uid 1000.Unfortunately all the internal scripts have permissions for a specific user, so if there is a line in
docker-compose.ymllikeuser: 2000, it will fail.The text was updated successfully, but these errors were encountered: