docker icon indicating copy to clipboard operation
docker copied to clipboard
verified publisher icon wallabag

table wallabag_internal_setting not found error after upgrade from 2.6.12 to 2.6.13

Open norweeg opened this issue 6 months ago • 2 comments

I upgraded from the 2.6.12 image to the 2.6.13 today and immediately started getting table not found: wallabag_internal_setting error and wallabag fails to start. Reverting back to 2.6.12, all other settings kept the same and wallabag starts without a problem. Database is mariadb 11.8.2 also running as a docker container.

norweeg avatar Jun 26 '25 15:06 norweeg

Weird, we didn't touch anything related to the database. Have you tried to check if all tables were still in the database?

j0k3r avatar Jun 27 '25 09:06 j0k3r

I did. I connected with DBeaver and the tables are still there and, like I said, when I reverted the wallabag image back to 2.6.12, everything was fine again. Other than checking if the database still contained the data, I never touched the database.

norweeg avatar Jun 28 '25 01:06 norweeg

Closing this because I retried using the latest tag (which, presumably, is 2.6.13 at the time of writing this) and I no longer get the table not found error.

norweeg avatar Jul 20 '25 21:07 norweeg