Ensure root_t label for /store #197
Conversation
|
The other thing I did briefly mess around with here is that in theory the existing |
|
Thoughts? |
There was a problem hiding this comment.
LGTM.
AIUI, this will not be necessary when we switch to using bootc install (osbuild/images#462).
Probably/hopefully yes, but OTOH I think this is generally right as a generic baseline anyways. |
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
|
LGTM |
github-merge-queue
bot
removed this pull request from the merge queue due to no response for status checks
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
|
OK this one just needs a quick re-stamp for approval, I just did a minor tweak to avoid a textual/logical conflict with #238 |
The way osbuild works is to synthesize a filesystem tree in the store, then copy it to the disk. This ensures the label for the store is `root_t` which ends up being the labeling for the "infrastructure" bits in the `/ostree` repository in the target root. This in turn is blocking a lot of things. Closes: osbuild#149
|
Oops, stray whitespace change still led to a conflict. Fixed. |
The way osbuild works is to synthesize a filesystem tree in the store, then copy it to the disk. This ensures the label for the store is
root_twhich ends up being the labeling for the "infrastructure" bits in the/ostreerepository in the target root.This in turn is blocking a lot of things.
Closes: #149