Backup & Restore - potential bug for wsl2 + docker desktop users

[entitycs]

Has anyone tried the backup/restore procedure?

If not, and if using wsl2 + docker desktop, it might be worth looking into...

...before updating docker desktop.

😒

[entitycs]

After updating through this latest large merge, and updating to docker desktop 4.83.0, I went to open the app, which threw me to the login page where my credentials no longer worked.

I looked at the docker logs, and sure enough, was greeted with my "new admin user + password".

Didn't lose anything important on my end. Still, maybe some safeguards should be in place that aren't? Leaving that for discussion, but mainly wanted to warn anyone who may have generated something important, in case whatever bug I hit finds them.

I am leaning towards docker being the culprit, but because I carried out both updates in one go, I'm not yet sure.

Is my data gone? Not entirely sure. Haven't checked the database. The data volume has not been renewed, but it contains empty memories, research, etc. A simple scheduled volume backup is probably what I'd lean toward if my app usage yielded critical data.

Other notes:

Since the docker update, I was immediately hit with the following error trying to build the latest from 'dev'.

Also, I had to change the searxng /tmp file handling, because Docker expects the template file to exist in /tmp (it doesn't - and it wasn't an issue before the docker update):

Binding to a folder containing the temp file, instead of binding the temp file itself alleviates that particular error.