systematic-debugging

The most robust course is to treat this as a root-cause mount visibility issue (likely SELinux labeling or container namespace visibility) rather than a missing file. Do not wrap or patch the application to ignore missing configuration until the mount is reliably visible inside the container. After confirming and correcting the mount visibility, consider a controlled fallback only if uptime requirements dictate, and only with explicit documentation and risk acceptance.