Description of problem: I often encounter this SELinux alert on fresh Fedora installs. SELinux is preventing bwrap from 'mounton' accesses on the ディレクトリー /tmp. ***** Plugin catchall (100. confidence) suggests ************************** bwrap に、 tmp directory の mounton アクセスがデフォルトで許可されるべきと考える場合。 Then バグとして報告してください。 ローカルのポリシーモジュールを生成すると、 このアクセスを許可することができます。 Do 以下を実行して、このアクセスを許可します: # ausearch -c 'bwrap' --raw | audit2allow -M my-bwrap # semodule -X 300 -i my-bwrap.pp Additional Information: Source Context unconfined_u:unconfined_r:thumb_t:s0-s0:c0.c1023 Target Context system_u:object_r:tmp_t:s0 Target Objects /tmp [ dir ] Source bwrap Source Path bwrap Port <不明> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-42.17-1.fc43.noarch Local Policy RPM selinux-policy-targeted-42.17-1.fc43.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 6.17.9-300.fc43.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Nov 24 23:31:27 UTC 2025 x86_64 Alert Count 2 First Seen 2025-12-02 16:15:42 PST Last Seen 2025-12-02 16:15:42 PST Local ID f9948e50-5d2b-44e8-894f-230d94647f00 Raw Audit Messages type=AVC msg=audit(1764720942.686:267): avc: denied { mounton } for pid=36667 comm="bwrap" path="/tmp" dev="tmpfs" ino=1 scontext=unconfined_u:unconfined_r:thumb_t:s0-s0:c0.c1023 tcontext=system_u:object_r:tmp_t:s0 tclass=dir permissive=0 Hash: bwrap,thumb_t,tmp_t,dir,mounton Version-Release number of selected component: selinux-policy-targeted-42.17-1.fc43.noarch Additional info: reporter: libreport-2.17.15 reason: SELinux is preventing bwrap from 'mounton' accesses on the ディレクトリー /tmp. package: selinux-policy-targeted-42.17-1.fc43.noarch component: selinux-policy hashmarkername: setroubleshoot type: libreport kernel: 6.17.9-300.fc43.x86_64 comment: I often encounter this SELinux alert on fresh Fedora installs. component: selinux-policy
Created attachment 2117689 [details] File: description
Created attachment 2117690 [details] File: os_info
*** This bug has been marked as a duplicate of bug 2415016 ***