Allow the Docker image to be run as a random user id#2325
Allow the Docker image to be run as a random user id#2325barkbay wants to merge 1 commit intoelastic:masterfrom
Conversation
|
This file is actually owned by the beats platform and will be overridden on the next beats update. We could add a custom Dockerfile template to support this but I'm not comfortable with using this for our generally distributed docker container images as I don't think strict perms shouldn't be relaxed by default. This is something we could solve in collaboration with @elastic/beats as they will/have likely run into the same issues. @barkbay Can you please open an issue describing the environment targeted more in depth so we can understand the issue better and help reach the right solution? |
|
Also, we don't have this in our docs but perhaps it applies here too? https://www.elastic.co/guide/en/beats/filebeat/master/running-on-kubernetes.html#_red_hat_openshift_configuration |
|
I will open an issue in the |
|
Issue has been opened here: elastic/beats#12686 |
|
Closed in favor of elastic/beats#12905 |
Hi,
I'm working on the compatibility of ECK with Kubernetes and Openshift.
On secured Kubernetes environments the user ID used to run a container is "random", you can't really predict it advance. Consequently we can't start the APM server container because it expects to be run with the user 1000 or 0 (root)
This PR brings some compatibility with such environments, based on the fact that on secured Kubernetes clusters and on Openshift the only thing you know is that the user is always a member of the root group.
You can find more details here: https://docs.openshift.com/container-platform/3.11/creating_images/guidelines.html#openshift-specific-guidelines
Thank you