fix: Add security context to init container #1300
Open
+4
−0
Conversation
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
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1300 +/- ##
=======================================
Coverage 94.74% 94.74%
=======================================
Files 42 42
Lines 2741 2741
=======================================
Hits 2597 2597
Misses 144 144 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
dan-fernandes
temporarily deployed
to
release
GitHub Actions
Inactive
dan-fernandes
changed the title
dan-fernandes
changed the title
dan-fernandes
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add security context to init containe.
Recently when updating P4X to v1.11.2 the following error is produced by the init-container:
error: failed to create directory /.cache/uv: Permission denied (os error 13)(I no longer have access to the full stack trace.)Best guess is that UV attempts to cache at
($HOME)/.cache/uvwhere$HOMEis not set due to the user not "existing". By defining a security context we force the init container to use a specific UID (by default1000) which should have a real home dir.