Cherry-pick #12905 to 7.x: Allow the Docker image to be run with a random user id#18634
Merged
jsoriano merged 1 commit intoelastic:7.xfrom May 19, 2020
Merged
Cherry-pick #12905 to 7.x: Allow the Docker image to be run with a random user id#18634jsoriano merged 1 commit intoelastic:7.xfrom
jsoriano merged 1 commit intoelastic:7.xfrom
Conversation
217192b to
7e5e882
Compare
Modify docker images so files required by beats are owned by group root, this follows Openshifts recommendations to run containerized applications with custom user ids. (cherry picked from commit 9dbdc15) Co-Authored-By: Michael Morello <michael.morello@elastic.co>
7e5e882 to
05d3b2f
Compare
Contributor
|
Pinging @elastic/integrations-platforms (Team:Platforms) |
Member
Author
|
run beats-ci/package |
Contributor
💔 Build Failed
Expand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Cherry-pick of PR #12905 to 7.x branch. Original message:
On secured Kubernetes environments (not only Openshift) the user ID used to run a container can't be known in advance. Consequently the APM server container can't be started on these environments because it expects to run with the user 1000 or 0.
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
See elastic/apm-server#2325 and #12686