Skip to content
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

Use elasticsearch user instead of root #669

Merged
merged 1 commit into from
Feb 23, 2022
Merged

Conversation

hgajjar
Copy link

@hgajjar hgajjar commented Feb 18, 2022

Until elasticsearch v7.9.3 it was working ok with the group being set as elasticsearch/1000, but since v7.16.2 it seems like it also requires the user to be set as elasticsearch/1000. This would make sure that the volume mount dir would be writeable by elasticsearch user.

Until elasticsearch v7.9.3 it was working ok with the group being set as `elasticsearch/1000`, but since v7.16.2 it seems like it also requires the user to be set as `elasticsearch/1000`. This would make sure that the volume mount dir would be writeable by elasticsearch user.
@andytson-inviqa andytson-inviqa force-pushed the misc/fix-es-permission-issue branch from 3f942a5 to 92992e9 Compare February 22, 2022 09:05
@hgajjar hgajjar merged commit 3b3bc44 into 1.3.x Feb 23, 2022
@hgajjar hgajjar deleted the misc/fix-es-permission-issue branch February 23, 2022 04:55
@andytson-inviqa andytson-inviqa added bug Something isn't working harness-all Changes required to all harness directories labels Apr 12, 2022
andytson-inviqa added a commit to inviqa/harness-docker that referenced this pull request Aug 15, 2023
Apparently elasticsearch is more picky with the volume mount
permissions.

Based on inviqa/harness-base-php#669
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working harness-all Changes required to all harness directories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants