-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
manifests: set proper SELinux labels for '/boot/efi' and '/boot/lost+found' #3912
base: main
Are you sure you want to change the base?
Conversation
4480ede
to
3327d6c
Compare
nice. I'll check it out! |
30e4814
to
1c188e0
Compare
I was playing around with this trying to use |
Do you have patch somewhere to check? |
1c188e0
to
b228d0d
Compare
@dustymabe indeed there was a small issue, now that fixed. I've added patch with |
322cfd5
to
11db312
Compare
added a few commits on top (the first one can be squashed into one of yours if you agree it adds value). Let me know what you think! |
LGTM, thx for your commits! |
5376f91
to
507c78a
Compare
…found' Issue: osbuild/osbuild#1877 Co-authored-by: Dusty Mabe <dusty@dustymabe.com>
This allows us to use the policy rather than hardcoding labels to set on the mountpoints. The unfortunate thing here is that in order to pick up a policy easily we have to use the `build` pipeline where the files are written out plainly and we don't have to find where the OSTree deployment is. I say unfortunate because right now for FCOS the `build` pipeline was getting skipped because we weren't using it for anything else, but now we'll be forced to build it. That's OK I think, because we really want to start using a non-host (i.e. non-COSA) buildroot for FCOS too if we can ever convince the team/community to get python into it. This commit also adds a comment to explain the "why" for the mkdir and two selinux stages.
60e36e9
to
3790fde
Compare
Issue: osbuild/osbuild#1877
ostree PRs: