Replies: 2 comments
-
Thank you for your question. I'm not sure which could be the problem, maybe for some reason you tempered the permissions? For sure, any new image of globaleaks can be run with old data since we always include migration scripts that would update the data for you. |
Beta Was this translation helpful? Give feedback.
-
I restarted version 5.10 from scratch using the backup from version 4.13. The database upgrade script progressed smoothly until version 68, at which point the following error occurred:
This seems to be related to permission issues, likely due to SELinux restrictions? My Solution: I moved the restored backup into a subfolder, e.g., /var/globaleaks/data, and updated the working path accordingly in the Dockerfile. |
Beta Was this translation helpful? Give feedback.
-
latest Dockerfile, same volumes, build without errors, nothing else changed
globaleaks | 2024-09-20T12:49:27+0000 [stdout#info] [E] ERROR: Cannot start GlobaLeaks. Please manually examine the exception.
globaleaks | 2024-09-20T12:49:27+0000 [stdout#info] [E] EXCEPTION: (sqlite3.OperationalError) unable to open database file\n(Background on this error at: https://sqlalche.me/e/14/e3q8)
any idea whats excactly the problem is? volume is present, database is present.
-rw------- 1 1337 root 1000K Sep 19 11:17 globaleaks.db
still have a 4.13 Backup. possible to start the 5.09 from the scratch with this backup?
thanks, regards, thomas
Beta Was this translation helpful? Give feedback.
All reactions