-
Notifications
You must be signed in to change notification settings - Fork 176
Elasticsearch container fails when running as non root. #34
Comments
close the issue. feel free to reopen |
Has this been fixed or why did you close? |
@weicongs-amazon sorry, I didn't reply there. I saw the comment and I accept that. Do you think we could run supervisord with the same UID as the container is running? |
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. |
We have identify the issue and have a solution proposed. |
Thank you for the update and the work! |
Status Update: this issue still remains open for the upcoming 1.9.0 release. |
Status Update: This issue is now fixed on both the plugins and the build sides. |
Thank you for fixing it! |
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.The text was updated successfully, but these errors were encountered: