Description of problem:
i attempted to stop a container with "machinectl stop container_name", and was denied. i would think systemd-machine would have proper permissions to interact with something labeled systemd_machine_t.
SELinux is preventing systemd-machine from 'kill' accesses on the cap_userns labeled systemd_machined_t.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that systemd-machine should be allowed kill access on cap_userns labeled systemd_machined_t by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'systemd-machine' --raw | audit2allow -M my-systemdmachine
# semodule -X 300 -i my-systemdmachine.pp

Additional Information:
Source Context                system_u:system_r:systemd_machined_t:s0
Target Context                system_u:system_r:systemd_machined_t:s0
Target Objects                Unknown [ cap_userns ]
Source                        systemd-machine
Source Path                   systemd-machine
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-40.28-1.fc40.noarch
Local Policy RPM              selinux-policy-targeted-40.28-1.fc40.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 6.10.12-200.fc40.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Mon Sep 30 21:38:25 UTC 2024
                              x86_64
Alert Count                   1
First Seen                    2024-10-09 01:36:43 EDT
Last Seen                     2024-10-09 01:36:43 EDT
Local ID                      d1e13b2d-7347-4617-a22a-3d91bee413ac

Raw Audit Messages
type=AVC msg=audit(1728452203.924:854): avc:  denied  { kill } for  pid=920 comm="systemd-machine" capability=5  scontext=system_u:system_r:systemd_machined_t:s0 tcontext=system_u:system_r:systemd_machined_t:s0 tclass=cap_userns permissive=0


Hash: systemd-machine,systemd_machined_t,systemd_machined_t,cap_userns,kill

Version-Release number of selected component:
selinux-policy-targeted-40.28-1.fc40.noarch

Additional info:
reporter:       libreport-2.17.15
reason:         SELinux is preventing systemd-machine from 'kill' accesses on the cap_userns labeled systemd_machined_t.
package:        selinux-policy-targeted-40.28-1.fc40.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.10.12-200.fc40.x86_64
comment:        i attempted to stop a container with "machinectl stop container_name", and was denied. i would think systemd-machine would have proper permissions to interact with something labeled systemd_machine_t.
component:      selinux-policy