In some contexts, filesystem mounts may be owned by unmapped users (e.g. emptyDir mounts in Kubernetes / OpenShift when using user namespaces). This causes systemd-tmpfiles(8) to fail, as a consequence of systemd's path processing routines which reject this scenario. systemd-tmpfiles "clones" exist and and can be used instead of systemd-tmpfiles. But beacuse the FreeIPA installer invokes /bin/systemd-tmpfiles directly, it is necessary to provide a mechanism (e.g. via environment variable) to specify that a different program should be used.
emptyDir
systemd-tmpfiles(8)
systemd-tmpfiles
/bin/systemd-tmpfiles
The feature can be restricted to the Fedora and RHEL container platform modules.
See freeipa-openshift-container PR that implements a systemd-tmpfiles clone: https://github.com/freeipa/freeipa-openshift-container/pull/35
Metadata Update from @ftweedal: - Issue assigned to ftweedal
master:
ipa-4-9:
Metadata Update from @frenaud: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)