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

After installing fapolicyd in image mode, the service fails to start with error "Failed writing db version No such file or directory".

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

fapolicyd-1.3.3-103.el10

fapolicyd-1.3.3-102.el9

How reproducible is this bug?:

Always

Steps to reproduce

1. Boot http://images.osci.redhat.com/RHEL-10.1-image-mode-x86_64.qcow2 (e.g. via "tmt run ... provision -h virtual --image ..." - see https://file.emea.redhat.com/~plautrba/journal/sealert_test_in_image_mode_using_tmt.html#org78ab700)

2. cat > Containerfile << EOF
   FROM images.paas.redhat.com/testingfarm/rhel-bootc:10.1
   RUN dnf -y install fapolicyd
   EOF
   
   # build the container image
   podman build -t localhost/test .
   
   # switch to the newly created container on next boot
   bootc switch --transport containers-storage localhost/test
   
   # reboot
   reboot 

1. Run "systemctl start fapolicyd".

Expected results

The service starts successfully.

Actual results

The service fails to start:

systemd[1]: Starting fapolicyd.service - File Access Policy Daemon...
fagenrules[1435]: /usr/sbin/fagenrules: No change
fapolicyd[1461]: 07/22/25 13:03:04 [ INFO ]: Can handle 524288 file descriptors
fapolicyd[1461]: 07/22/25 13:03:04 [ INFO ]: Ruleset identity: 0a028cfb95e93569d565d732890384b69952d7841d10af060e3ff13af07842d9
fapolicyd[1463]: Initializing the trust database
fapolicyd[1463]: Trust database migration will be performed.
systemd[1]: Started fapolicyd.service - File Access Policy Daemon.
fapolicyd[1463]: Failed writing db version No such file or directory
systemd[1]: fapolicyd.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: fapolicyd.service: Failed with result 'exit-code'.