-
Notifications
You must be signed in to change notification settings - Fork 6
Add support for SELinux systems #255
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
base: feat/selinux
Are you sure you want to change the base?
Conversation
|
Thanks a lot for the PR ❤️ |
1e2df23 to
0eff362
Compare
|
(This is a rebase to keep the diff readable.) |
|
After taking a look at the contexts of the files, I'm not sure that we can solve this by just changing the files. Someone with knowledge of selinux might be able to find a common label that makes the files available to all containers, but I can't. :) And I don't think a The I still need to take a look at |
|
We seem to need the |
|
@YtvwlD could you please rebase your branch based on the new |
|
As @Threated tells me, this is actually a horror rebase. I will try to cherry pick your commits into the branch. As this PR has relevant discussion, I leave it open for now. |
This is the other half of the changes we talked about last week: Since we're running the new VM with RHEL, we need some adjustments for SELinux. These are ignored on systems without it.
Adding
Zallows this container (and only this one) to access the bind mount. This seems to be only needed for files in/srv, because RHEL ships a special label for this folder.This is also why
/srv/docker/bridgehead/bridgeheadcan be run manually, but not from a systemd service.We additionally had the slight problem that with Podman,
/var/run/docker.sock, being a symlink to/var/run/podman/podman.sock, was owned byroot:root. Changing this toroot:dockerworked, but I'm not quite sure where to put it in the existing scripts. (dockeris the usual Docker cli.)@Threated