-
-
Notifications
You must be signed in to change notification settings - Fork 225
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
fix(ES image): Allow running Elasticsearch 5 container as any user #62
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
orangejulius
added a commit
that referenced
this pull request
Jan 16, 2019
In #55 we added a `chown` line that attempts to set proper permissions on the Elasticsearch data directory. `chown` can generally only be run as root, so this PR adds handling for the common case where `chown` fails. In general, either the pelias CLI is run as root, and the `chown` will succeed, or the CLI is run as the same user the Docker container processes will run as. In this case the `mkdir` on the preceeding line will set up the directory with proper ownership. We can't really do anything in an automated way to handle people running the Pelias CLI as a different, non-root, user than the one they want the containers to run with, so I think this is the best we can do. This will be even more useful once #62 is merged.
orangejulius
added a commit
that referenced
this pull request
Jan 16, 2019
In #55 we added a `chown` line that attempts to set proper permissions on the Elasticsearch data directory. `chown` can generally only be run as root, so this PR adds handling for the common case where `chown` fails. In general, either the pelias CLI is run as root, and the `chown` will succeed, or the CLI is run as the same user the Docker container processes will run as. In this case the `mkdir` on the preceding line will set up the directory with proper ownership. We can't really do anything in an automated way to handle people running the Pelias CLI as a different, non-root, user than the one they want the containers to run with, so I think this is the best we can do. This will be even more useful once #62 is merged.
missinglink
approved these changes
Jan 17, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
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
force-pushed
the
elasticsearch-any-user
branch
from
January 17, 2019 20:41
3918031
to
7aeff77
Compare
The |
calpb
pushed a commit
to sorelle/docker
that referenced
this pull request
Mar 29, 2021
In pelias#55 we added a `chown` line that attempts to set proper permissions on the Elasticsearch data directory. `chown` can generally only be run as root, so this PR adds handling for the common case where `chown` fails. In general, either the pelias CLI is run as root, and the `chown` will succeed, or the CLI is run as the same user the Docker container processes will run as. In this case the `mkdir` on the preceding line will set up the directory with proper ownership. We can't really do anything in an automated way to handle people running the Pelias CLI as a different, non-root, user than the one they want the containers to run with, so I think this is the best we can do. This will be even more useful once pelias#62 is merged.
calpb
pushed a commit
to sorelle/docker
that referenced
this pull request
Mar 29, 2021
fix(ES image): Allow running Elasticsearch 5 container as any user
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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