Import worker uses empty SQLite database instead of migrated database (SqliteError: no such table: importStagingBookmarks) #2931
Unanswered
BinderManfred
asked this question in
Q&A
Replies: 2 comments
-
|
There's a bunch of problems here.
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
As requested: manfred-binder@manfred-binder-iMac13-1:~/karakeep$ cat docker-compose.yml meilisearch: karakeep: manfred-binder@manfred-binder-iMac13-1:~/karakeep$ |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Environment
Docker Compose
Only
/datais mounted as a volume.Problem
The container starts successfully and database migrations are executed.
However, the import worker continuously logs:
The error repeats every few seconds.
Logs
Investigation
I inspected all SQLite databases inside the container.
The migration database contains the expected table:
Using better-sqlite3:
returns:
However:
do not contain this table.
In fact, both files are automatically created as empty databases:
Running the same SQL query shows:
Additional information
Expected behaviour
The import worker should use the migrated SQLite database (or create the required schema automatically) instead of opening a newly created empty database.
Actual behaviour
The import worker appears to open an empty SQLite database located at:
which results in:
and the import worker never becomes functional.
Any ideas what could cause the worker to use a different SQLite database than the migration process?
produced with Chat GPD
Beta Was this translation helpful? Give feedback.
All reactions