Fix selinux for vtoycow in CreatePersistentImg.sh #2651
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
|
This could also be done more elegantly at runtime, however I was not able to find code related to the initialization of the vtoyoverlayfs in this repo + I am assuming that |
Label the overlayfs root directory in vtoycow imgs with the appropriate selinux context to enable booting without disabling selinux.
0xF4CED
force-pushed
the
vtoycow-selinux-bootfix
branch
from
57a7b23 to
e6bba31
Compare
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.
Label the overlayfs root directory in vtoycow imgs with the appropriate selinux context type to enable booting without disabling selinux.
Note
There will still be issues with selinux when you start digging into the system, e.g. installing packages. But booting and basic usage works fine, and you can disable selinux/enforcing from there when necessary.