Database lost after recreating docker container

[Madic-]

Hello,

after recreating the docker container, the following files would get lost when not placed somewhere else because they only exist in the container:

• goEDMS.db
• simpleEDMSIndex.bleve

Can you extend the docker installation documentation with a way, to also persist those files?

[deranjer]

Yes, sorry, this is just a dumb mistake on my part, my inexperience with docker showing. I'll fix that in the next hotfix.

[deranjer]

Hmm, so trying to figure this out actually, first time using docker. Both database files are generated by the executable on run time, do I just do two more mounts for both those files? Seems like a whole lot of config options. I'll be doing more research I think.

[Madic-]

Just creating two more volume mounts are problematic because at first run, both files do not exist. I think best would be creating a subfolder (like ./data) where all files reside. Than only the ./data folder needs to be mounted. And beneath this ./data directory you can save the database, log and config file. Though this could be a breaking change for current installations.

An approach could be creating environment variables where you can define the location of various config files or config directories inside the container. Many dockerised applications are doing this.

[deranjer]

Okay, I moved everything to the "databases" folder and mounted that, and that seems to work. Please check the documentation and try it again.

[Madic-]

Thank you. That worked. From my point of view this issue can be closed