Help with read-only config files - I need a workaround

[Daniel Kasak]

Hi all. I've had a long-standing issue with some bizarre interaction
between unixodbc and some 3rd-party binary drivers ( Netezza drivers
). It seems that for Netezza, we need *both* the global odbcinst.ini
*and* ~/.odbcinst.ini files to be identical. If they're not, very
strange things happen. I have tried getting support from unixodbc
people and IBM - no such support is coming.

My application is managing the contents of ~/.odbcinst.ini ( by
writing the file on startup ). It's dynamically generated, as we allow
users to download and install their own ODBC drivers ( re-distribution
is forbidden ).

For things to work with Netezza, we need that global odbcinst.ini to
exist and for the Netezza section to be identical to the one we
generate. Is this possible, somehow? The contents of /etc are
read-only in the flatpak container. I tried using bind mounts ( which
I'm not familiar with, but thought it might work ), but bind mounts
are apparently only available as root. What other options might allow
me to make that global file appear to be a mirror of the local one?

Dan