HonkyTonk

Hello everybody, last week I upgraded from Unraid 6.9.2 to Version 6.12.2. After that I got some error messages like - general protection fault, probably for non-canonical adress... - BTRFS critical (device loop2): corrupt leaf. block... These were caused by a corrupted docker image. I learned that, in this case, you can basically get rid of this image and simple build a new one, since the templates (for building the container) and the appdata is stored outside of the image. So after rebuild all standard Community Application container, I recreated the only container deployed via Docker-Compose (Teslamate), and all the data was missing . After some research I learned that its volumes are basically stored in the docker.img. Luckily I didn't deleted the corrupt, old image. I managed to mount it again, only starting the teslamate container and was able to do a backup. Now, the following things: - first of all do backups - second: everybody who is using docker-compose: make sure to persist the data outside of the docker image (I almost lost 2 years of driving data and felt really bad) - and lastly: are there any best practices on persisting data in unraid? I would simply manually editing the yml and mapping the volumes to the corresponding appfolder (in this case /appdata/teslamate)

Thank you. for the fast response, saved me probably 2 more hours of debugging and frustration Maybe you can add a list of supported / tested vpn provider in the readme of the docker for other users.

Hi @ich777: I got the exact same issue. Could you please share the solution, if you found one?

Had the same issue. The creator of the docker container modified the Docker variables. Edit your tt-rss container, take a look on the Variables and fill them correctly. According to the error message you are using Postgres as Database. eg. in the Variable TTRSS_DB_TYPE you have to type "pgsql" instead of "mysql". In my case I had to fill out everything again (DB Type, Host, User, Pw, Name etc.). No clue how and why this happened, because I setup the container month ago and didn't update it since then.