Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Elasticsearch container fails when running as non root. #34

Closed
jkrnak opened this issue Nov 14, 2019 · 10 comments
Closed

Elasticsearch container fails when running as non root. #34

jkrnak opened this issue Nov 14, 2019 · 10 comments
Assignees
Labels
Docker Docker image related issues enhancement New feature or request

Comments

@jkrnak
Copy link

jkrnak commented Nov 14, 2019

When running the container as non root, ie with securityContext.runAsUser: 1000 the supervisord process was starting up as the passed in user.
This caused supervisord to fail because the /usr/share/supervisor directory was owned by root.

@alolita alolita added the bug Something isn't working label Apr 20, 2020
@weicongs-amazon weicongs-amazon added enhancement New feature or request and removed bug Something isn't working labels May 26, 2020
@weicongs-amazon
Copy link
Contributor

close the issue. feel free to reopen

@jkrnak
Copy link
Author

jkrnak commented Jun 16, 2020

Has this been fixed or why did you close?

@weicongs-amazon
Copy link
Contributor

@jkrnak we shared some comments in the PR #31
We think it's not a good way to grant permissions to all of the users. pls share your idea here.

@jkrnak
Copy link
Author

jkrnak commented Jun 16, 2020

@weicongs-amazon sorry, I didn't reply there. I saw the comment and I accept that.
But currently the es image can't run without root privileges (at least if opendistro_performance_analyzer is enabled), which makes it difficult to run on shared (multi tenant) clusters.

Do you think we could run supervisord with the same UID as the container is running?

@weicongs-amazon
Copy link
Contributor

weicongs-amazon commented Jun 16, 2020

Thanks @jkrnak. Agree with you. This is valid point. We should use the same UID. And there should be an alternative way to start the performance analyzer to avoid the supervisord. Let me sync up with the team firstly. will post updates here.

@peterzhuamazon peterzhuamazon added the Docker Docker image related issues label Jun 17, 2020
@peterzhuamazon
Copy link
Contributor

We have identify the issue and have a solution proposed.
We are working on it and hopefully will give you an update soon.
Thank you again for your inputs.

@jkrnak
Copy link
Author

jkrnak commented Jun 25, 2020

Thank you for the update and the work!

@peterzhuamazon
Copy link
Contributor

Status Update: this issue still remains open for the upcoming 1.9.0 release.
We plan to push the changes after this release as it requires testings from specific plugin.

@peterzhuamazon
Copy link
Contributor

Status Update: This issue is now fixed on both the plugins and the build sides.
Will use this new config in the next releases. This issue will be closed as of now.
Thanks @jkrnak for reporting this and sorry for the delay to get it eventually fixed in ODFE.

@jkrnak
Copy link
Author

jkrnak commented Jul 14, 2020

Thank you for fixing it!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Docker Docker image related issues enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants