I'm running SearXNG as a home rootless podman service. I want to share the configuration file and cache directory from my host. Setting up ~/.config/searxng/settings.yml and ~/.cache/searxng using home-files-service-type works, but when starting the container, the container takes ownership of the folders/files with it's own searxng:searxng user (166512:166512). When I reconfigure my home again, home-files-service-type fails because it doesn't have access to the location.
Right now, I have a hack where I rather use home-activation-service-type and only create the folders if they don't exist, and only symlink the settings if it doesn't exist. This is broken because changes in my settings wont be reflected back to the container. I thought about adding 166512 as a group in my system and give my user this group to be able to manipulate the locations, but that will leak the implementation out of my home to my system. Any ideas on how to best handle this situation?
signature.asc
Description: PGP signature
