Description of problem: This happens when I start podman container with binded host directories. SELinux is preventing metadata-provid from 'write' accesses on the file ContactDataMigrate.orx. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that metadata-provid should be allowed write access on the ContactDataMigrate.orx file 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 'metadata-provid' --raw | audit2allow -M my-metadataprovid # semodule -X 300 -i my-metadataprovid.pp Additional Information: Source Context system_u:system_r:container_t:s0:c48,c687 Target Context unconfined_u:object_r:user_home_t:s0 Target Objects ContactDataMigrate.orx [ file ] Source metadata-provid Source Path metadata-provid Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-38.8-1.fc39.noarch Local Policy RPM selinux-policy-targeted-38.8-1.fc39.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 6.3.0- 0.rc1.20230309git6a98c9cae232.18.fc39.x86_64+debug #1 SMP PREEMPT_DYNAMIC Thu Mar 9 23:54:03 +05 2023 x86_64 Alert Count 1 First Seen 2023-03-10 11:13:22 +05 Last Seen 2023-03-10 11:13:22 +05 Local ID a13d8206-4247-45c9-964c-393511ad89ba Raw Audit Messages type=AVC msg=audit(1678428802.973:413): avc: denied { write } for pid=61968 comm="metadata-provid" name="ContactDataMigrate.orx" dev="nvme1n1" ino=750708 scontext=system_u:system_r:container_t:s0:c48,c687 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1 Hash: metadata-provid,container_t,user_home_t,file,write Version-Release number of selected component: selinux-policy-targeted-38.8-1.fc39.noarch Additional info: reporter: libreport-2.17.8 reason: SELinux is preventing metadata-provid from 'write' accesses on the file ContactDataMigrate.orx. package: selinux-policy-targeted-38.8-1.fc39.noarch component: selinux-policy hashmarkername: setroubleshoot type: libreport kernel: 6.3.0-0.rc1.20230309git6a98c9cae232.18.fc39.x86_64+debug comment: This happens when I start podman container with binded host directories. component: selinux-policy
Created attachment 1949472 [details] File: description
Created attachment 1949473 [details] File: os_info
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.
This message is a reminder that Fedora Linux 39 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '39'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 39 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26. Fedora Linux 39 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.