Open leaf-node opened 1 month ago
Here's the apparmor config: apparmor_php-fpm.txt (The markdown formatting was broken).
I don't run AppArmor, I use SELinux. But perhaps: The --security-opt apparmor=unconfined option does not set any further confinement, if the process running Podman is confined, then the container will continue the confinement.0
As a workaround, I placed the folllowing in /etc/apparmor.d/local/php-fpm
:
# vim: ft=apparmor
# for Zabbix server in podman container
/etc/php83/** r,
/usr/share/zabbix/** r,
/usr/share/php83/** r,
/etc/zabbix/** r,
/tmp/php-fpm.sock rw,
/tmp/php-fpm.pid rw,
Then ran:
systemctl reload apparmor.service
A friendly reminder that this issue had no activity for 30 days.
Issue Description
Similar to #8575, Apparmor from the host is active inside of containers despite use of
--security-opt apparmor=unconfined
. I am running OpenSUSE Leap on an x86_64 machine.Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
Once the DB is initialized, the log command above shows the following output:
Describe the results you expected
I expected
php-fpm
to start in the Podman container.podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
No response
Additional information