-
Bug
-
Resolution: Unresolved
-
Major
-
rhel-10.0
-
selinux-policy-40.13.10-1.el10
-
No
-
Low
-
3
-
rhel-sst-security-selinux
-
ssg_security
-
12
-
1
-
QE ack
-
False
-
-
No
-
SELINUX 240925 - 241016, SELINUX 241016 - 241106, SELINUX 241106 - 241127
-
-
Pass
-
Automated
-
Unspecified Release Note Type - Unknown
-
None
$ podman run --pull=newer --rm -ti quay.io/centos/centos:stream10-development [root@bf0d79a31a06 /]# dnf -y install selinux-policy-targeted ... Running scriptlet: selinux-policy-targeted-40.13.9-1.el10.noarch 9/11 Could not set context for /var/lib/selinux/targeted/tmp/modules/100/abrt/cil: Operation not supported Could not set context for /var/lib/selinux/targeted/tmp/modules/100/abrt/hll: Operation not supported Could not set context for /var/lib/selinux/targeted/tmp/modules/100/abrt/lang_ext: Operation not supported Could not set context for /var/lib/selinux/targeted/tmp/modules/100/abrt: Operation not supported Could not set context for /var/lib/selinux/targeted/tmp/modules/100/accountsd/cil: Operation not supported ... repeats *a lot*
RHEL packages in general need to handle the case when they are being installed inside a podman or similar container. One way to do that is "systemd-detect-virt -c", another is via stat -f /run/.containerenv.
- relates to
-
RHEL-70632 Lots of "Could not set context for /var/lib/selinux/targeted/tmp/modules/...: Operation not supported" messages when building image mode images
-
- Release Pending
-
- links to
-
RHBA-2024:140162 selinux-policy bug fix and enhancement update