This repository has been archived by the owner on Jan 21, 2021. It is now read-only.
Fix error breaking non-root policy mongodb #30
Conversation
This file contains 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
Hi, i've spotted the "Error: container's runAsUser breaks non-root policy" in my events and traced it down to, the securityContext runAsUser/fsGroup. The chart defaults (https://github.com/helm/charts/blob/e1b97b9232d7273127f53c7899d2377d5912f267/stable/mongodb/values-production.yaml#L113) already specify runAsUser and fsGroup 1001 and mongodb starts successfully with this configuration. A bit strange tho' because there is no UID/GID defined 1001 in the container.
mlandauer
added a commit
to mlandauer/flux-get-started
that referenced
this pull request
Mar 30, 2020
|
I found the same issue. Though I wonder whether this is here on purpose to show the GitOps workflow of fixing it, pushing and seeing the cluster correct itself. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Hi,
i've spotted the "Error: container's runAsUser breaks non-root policy" in my events and traced it down to, the securityContext runAsUser/fsGroup.
The chart defaults (https://github.com/helm/charts/blob/e1b97b9232d7273127f53c7899d2377d5912f267/stable/mongodb/values-production.yaml#L113) already specify runAsUser and fsGroup 1001 and mongodb starts successfully with this configuration.
A bit strange tho' because there is no UID/GID defined 1001 in the container.