(Bug report) - Update to docker latest issue with DB version

[stanthewizzard]

Trilium Version

0.62 latest

What operating system are you using?

Other Linux

What is your setup?

Local (no sync)

Operating System Version

Photon Docker

Description

After updating to the latest version. Issue with DB version

Thanks for help

Error logs

Current DB version 228 is newer than the current DB version 227, which means that it was created by a newer and incompatible version of Trilium. Upgrade to the latest version of Trilium to resolve this issue.

[Daerendor]

Can reproduce on version 0.62.6 in Docker container.

[rom1dep]

Perhaps https://github.com/zadam/trilium/discussions/4596 ?

[Daerendor]

Perhaps #4596 ?

Solved for me. My image was updated to 0.63-beta.

[stanthewizzard]

Solved for me too. My image was updated to 0.63-beta.

[skellyatsnhu]

Same issue with the latest tag. Switching to 0.63-beta does fix it, but the latest tag exhibits the problem still.

[Vexz00]

Same here but I use the 63.1-latest tag and now it works.

[Heidieker]

I used the following solution to temporarily solve the problem, but I'm not sure if new problems will occur.

# Stop the service from running
# Then modify the database version
sqlite3 document.db
UPDATE options SET value='227.0' WHERE name='dbVersion';

Great! Thank you. Simple solution is working for me. Open it in sqlite command line tool

.open document.db
UPDATE options SET value='227.0' WHERE name='dbVersion';
.save document.db
.exit

[rom1dep]

@jan-bar @Heidieker : please don't do/recommend doing that: you are practically bypassing the mechanism which ensures that the application code remains in line with the data model. This is begging for trouble (features which got updated might break and you might even lose data). Moreover, when the application code will ultimately be updated, the migrations process will fail, and you will be left with an application refusing to start.

The solution is simple and was mentioned several times above: just point your image to the correct version.

[Nriver]

Avoid manually altering the version number. Manual adjustments could result in your data being migrated twice, leading to potential data errors.

[Heidieker]

and you will be left with an application refusing to start.

Thats why i changed the version number, because the application did not start. Now its starting and i can save my notes.

[rom1dep]

and you will be left with an application refusing to start.

Thats why i changed the version number, because the application did not start. Now its starting and i can save my notes.

And probably soon, it won't start, again (due to the migrations being attempted against a version the db is already at).

You are circumventing protections here, opening the door to unintended consequences. The point of my message was to make that crystal clear.

[Heidieker]

Thank you

[LivingWithHippos]

Same here but I use the 63.1-latest tag and now it works.

Can confirm that this is the solution, this is probably what happened

• latest pointed to 0.63 and the db got updated to version 228
• 0.63.1 came out and got published as 63.1 by mistake, also latest now points to 0.62.6 which supports db version 227

the solution is to switch to this image until 0.63.1-latest gets republished and linked to latest (or 0.64 comes out)

services:
    trilium:
        # image: zadam/trilium:latest
        image: zadam/trilium:63.1-latest

[e-p-s]

Can you please fix this ASAP. Cant access my notes anymore. Current DB version 228 is newer than the current DB version 227.