Updating Container #4
Description
Hello,
I've found that in order to maintain my container's configuration through restarts and upgrades, I need to map the /usr/local/openvpn_as/etc folder to a persistent volume.
However, when the container updates during a restart event (e.g. from 2.1.2 to 2.1.9), the mapped folder doesn't receive the updated assets/processes (e.g. database updates, new client versions, etc.)
Would it make sense to move the actual installation of the OpenVPN AS deb file to the init script vs the Dockerfile? This way any updates will take effect on the mapped volume for those of us that need to keep the configuration persistent - it'd just add the time to install the package during startup.