ERROR: Current DB version 228 is newer than the current DB version 227

[thehijacker]

My docker instance of Trilium would not start anymore. Looking at logs I can see:

ERROR: 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.

But I am using latest docker image in docker-compose:

  trilium:
    image: zadam/trilium
    container_name: trilium
    environment:
      - TZ=Europe/Ljubljana
    ports:
      - 18080:8080
    volumes:
      - /mnt/usb_1/Docker/Trilium/data:/home/node/trilium-data
    restart: unless-stopped

Any idea how I can fix this? Thank you.

[rom1dep]

If your docker deployment is synced with "latest", could it be that you pulled 0.63-beta previously, and 0.62.6 (just released) thereafter?

Note that the docs discourage using latest for this specific reason: https://github.com/zadam/trilium/wiki/Docker-server-installation

You should be able to sync up with 0.63-beta again

[thehijacker]

I have change to 0.63.1-beta and it starts again. I will wait for next major and fix the tag to it once available. Thank you for your help.

[meichthys]

Related to #4590

[aashish108]

Whats the next major version? When 0.63.1-beta comes out of beta?

[zandhaas]

Note that the docs discourage using latest for this specific reason: https://github.com/zadam/trilium/wiki/Docker-server-installation

LATEST: should be the lastest STABLE version not some beta version or other not well functioning version.

[GitTimeraider]

Note that the docs discourage using latest for this specific reason: https://github.com/zadam/trilium/wiki/Docker-server-installation

LATEST: should be the lastest STABLE version not some beta version or other not well functioning version.

Kinda have to agree with this. The only Docker container ive ever seen that discourages using the latest tag :P

[barrettsoftware]

I have this same problem. I have never seen a docker image that uses "latest" as beta branch lol.

I tried relaunching container with zadam/trilium:0.63.1-beta but it fails with error 400

[mzrimsek]

I had to recreate the container completely with the same volume mappings and everything and it worked for me. Might be worth trying?

I also agree that latest not being the image tag to use is quite bizarre.

[barrettsoftware]

I did get it working. Thank you to those who posted solutions

[DysfunctionalProgramming]

I ran into the same problem and solved it by pointing at the beta tag. Out of the 20 docker containers I have running this is the only one that is not safe using latest tag :/

[dada051]

It's not the first and only dockerised app that use "latest" tag as beta/RC branch, but when they do it, they have also a "stable" tag (i.e netdata). And if you RTFM, you know that you should not use "latest".

[lumper5]

Stable would be a nice alternative, were it to exist in this schema.

[yllekz]

Honest guestion - Can you name what other docker apps do this? I've never heard of using an industry standard "latest" tag as the beta. I have 50+ unique docker containers and they all revolve around using "latest" for the stable build. Beta is "nightly" or "x.x.x-beta"

[catduckgnaf]

Latest exists, and latest should not go to an "earlier" version.
I've seen latest and develop which is fairly standard.

I got it working, but feel latest should always be latest stable, thats how I have always seen it done.

[zadam]

I'm sorry for this mistake. I believe this was caused by this strange tag which doesn't follow the convention (leading "0.", doesn't contain the "-beta" suffix) which caused it to be tagged as "latest".

I don't understand how this tag was created. I don't think it happened ever before. I will watch out for this when publishing new 0.63 release.

[tidalvirus]

My main curiosity here, after reading that Trilium is now in 'maintenance mode', when do you think we can safely switch back to the 'latest' tag? Would be nice to get my config back to normal before I forget about this small hiccup :)

[neurosurgeon]

So what is the fix for now?

[jieny]

How to resolve this issue?
Keep my data unchanged.
What should I do when I want to go back to the old version?