shellcheck_run_steps: use :Z volume mount for SELinux relabeling if supported
#19
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
… suppored Signed-off-by: Arthur Exaltação <arthur.exaltacao@chainguard.dev>
tulilirockz
changed the title
:Z volume mount for SELinux relabeling if suppored:Z volume mount for SELinux relabeling if supported
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This is usually required on systems that use SELinux due to labeling issues.
:Zmakes it so an unique SELinux label gets written to all the files under (mount) so that only the container running can access it,:zis the same thing but if you want to share directories between containers. This should resolve an issue where running the shellcheck hook breaks on Fedora/SELinux-enabled systems and should be a no-op for non SELinux-enabled systems/MacOSI haven't been able to test this as I don't have any virtual machine with SELinux enabled, but definitely does not break anything on my end on MacOS - would like some more testing from other people, though!