Open tokejepsen opened 4 years ago
Somehow? :O
I would recommend you don't use volumes, but mount an existing volume off disk. It won't do well on Windows, which is why I would also recommend you host the database elsewhere. Volumes and Docker are kind of transient; they aren't meant for persistence (as far as I know) but more as a temporary storage location. I use them in tutorials and such because they're easy, but for production definitely host an actual db somewhere.
I know it's not the best solution but the overhead on the management of actual database is not worth it for us atm. Use the docker image has been working great for 6 months, except for these two occasions, and with the backup feature in this repo we can restore the database in seconds.
It's something to warn against for other users though. As a solution for us atm, is to take more frequent backups, which is not a bad thing anyways.
Issue
We have been using this image for production for a while. We routinely take backups of the database each day, so restoring is not an issue.
The issue we have faced twice now, is that the volume were the database gets stored are somehow purged without user interaction.