What were you trying to do that didn't work?

After bootc switch to a bootc container image including php-fpm, in a system which didn't had php-fpm installed before the switch, it fails to start with:

ERROR: failed to open error_log (/var/log/php-fpm/error.log): No such file or directory (2)

The php-fpm package creates the /var/log/php-fpm/ in its RPM scripts, but changes to /var are NOT applied during bootc switch and bootc upgrade, only during initial provisioning (bootc install) of image mode systems.

To make it work reliabily in image mode, it should use systemd-tmpfiles to create its log directory, from a configuration file such as:

echo 'd /var/log/php-fpm 0755' > /usr/lib/tmpfiles.d/php-fpm.conf

What is the impact of this issue to you?

Please provide the package NVR for which the bug is seen:

How reproducible is this bug?:

Always

Steps to reproduce

1. Provision a system, using image mode, which does NOT have the php-fpm package installed
2. bootc swtich or update to a bootc image which includes the php-fpm package and httpd service enabled
3. The php-fpm systemd unit fails to start

Expected results

php-fpm starts fine after bootc switch or update

Actual results

php-fpm fails with error "failed to open error_log (/var/log/php-fpm/error.log): No such file or directory (2)"