-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Upgrade to F31: SELinux denials with container_t trying to access spc_t #4361
Comments
@rhatdan PTAL |
I can trigger this on fresh Fedora 31. CentOS 8 systemd root container, running rabbitmq-server. From outside the container
See AVCs:
The command still works, though. |
Reproducer on a fresh Fedora 31:
On the host run See
|
Do you know what process is running as spc_t? ps -eZ | grep spc_t |
@rhatdan it is the externally exec'ed program
|
That is a bug. |
PR has merged that should fix this. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
After upgrading from Fedora 30 to Fedora 31, I am getting SELinux denials when container_t is trying to acess spc_t data. This doesn't prevent the container from functioning, though.
Any ideas where all this spc_t access is coming from?
Steps to reproduce the issue:
Upgrade from Fedora 30 to Fedora 31
Create a CentOS 8 container with /sbin/init as entrypoint
Do moderately complicated stuff like:
Describe the results you received:
Lots of SELinux denials mesages when container_t tries to access spc_t data.
Everything still works(!) and the container runs without any issues even when enforcing is on.
Describe the results you expected:
Clean ausearch -m avc output.
Additional information you deem important (e.g. issue happens only occasionally):
Need below to silence SELinux.
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Additional environment details (AWS, VirtualBox, physical, etc.):
Upgraded baremetal from F30 to F31. Sample AVC messages:
The text was updated successfully, but these errors were encountered: