Upgrading/migrating a zadam Trilium docker container to a Trilium Next one?

[maphew]

What's the process for upgrading or migrating a zadam Trilium docker container to a Trilium Next one?
Are there any stake filled pits and foot guns to be wary of?

[meichthys]

Download the new version and run it. That's it. No traps :)
For docker, just update your compose file with the new TriliumNext image from dockerhub.

We get this question enough that we should probably add a section to the readme to clarify this.

[maphew]

I'm a docker noob, and in this case am using it via Synology's "Container Manager". Once I figure how to locate and edit the compose file, what do I use for the TNext image name?

[meichthys]

https://github.com/orgs/TriliumNext/discussions/369#discussioncomment-10455561

[eliandoran]

@maphew , the corresponding image name would be triliumnext/notes:latest

You can find an example on the new Docker compose file here: https://github.com/TriliumNext/Notes/blob/develop/docker-compose.yml

[maphew]

thanks!
...it looks like I have homework and research to do in understanding docker, and Synology's use of it. Editing the image name in-place is disabled and I don't want to risk running 2 containers against one database. Well, off to school then!

[uniquegch]

I started using zadam/trilium this year and just discovered it is in Maintenance Mode. I have one Server docker based and a couple of clients as Desktop version running on Arch or Debian (12,13).
I did first upgrade the server and for that I only changed the image information in my docker-compose.yaml file. This "inplace" upgrade works and I can also use the Trilium 0.63.7 Desktop version with the server now running TriliumNext Notes. Changes are being synced in both directions.

Here are my steps for the upgrade of the docker-compose.yaml file

1. ssh into the server
2. cd /path/to/trilium/container ### my docker container for trilium is names trilium
3. docker compose stop
4. cp docker-compose.yaml docker-compose.yaml.zadam ### docker-compose.yml or docker-compose.yaml is the same
5. nano docker-compose.yaml
6. change image from image: zadam/trilium:latest to triliumnext/notes:latest ### see the two docker-compose file below
7. cd ..
8. cp -r tilium trilium.bak ### just have a backup in case the inplace upgrade goes sideways
9. cd trilium
10. docker compose pull ### see the output from my machine
11. docker compose up
12. docker compose logs trilium ### see the output from my maschine and the container_name stays trilium
13. open a webbrowser and enter the URL/IP of the trilium server with port (I am using heimdall as dashboard and click on the trilium link)
14. login if necessary and click on the flower icon top left. it should show "About TriliumNext Notes"

Below the docker-compose.yaml file ### I am running Docker Compose version v2.29.2 and docker-ce Version: 27.2.1

### trilium version from zadam
services:
 trilium:
   image: zadam/trilium:latest
   container_name: trilium
   hostname: trilium
   restart: unless-stopped
   ports:
     - '8201:8080'  ### I am using 8201 in the webbrowser
   environment:
     - PUID=1000
     - PGID=1000
   volumes:
     - ./trilium-data:/home/node/trilium-data  ### I store the data within the container itself thats why ./trilium-data

### triliumnext notes version
services:
 trilium:
   image: triliumnext/notes:latest
   container_name: trilium
   hostname: trilium
   restart: unless-stopped
   ports:
     - '8201:8080'  ### I am using 8201 in the webbrowser
   environment:
     - PUID=1000
     - PGID=1000
   volumes:
     - ./trilium-data:/home/node/trilium-data  ### I store the data within the container itself thats why ./trilium-data

### Output from docker compose pull
[+] Pulling 15/15
 ✔ trilium Pulled                                                                                  30.7s 
   ✔ 5de87e84afee Pull complete                                                                     4.1s 
   ✔ ea0c2787dcd2 Pull complete                                                                     4.1s 
   ✔ e971a37af272 Pull complete                                                                     6.7s 
   ✔ 31bc2c2b669f Pull complete                                                                     6.8s 
   ✔ 7862ea6566a7 Pull complete                                                                     6.9s 
   ✔ 9ff11a6775af Pull complete                                                                    13.6s 
   ✔ 940be1f82a18 Pull complete                                                                    13.6s 
   ✔ 59ee54b77aeb Pull complete                                                                    14.1s 
   ✔ 8dd8ed95a18f Pull complete                                                                    14.1s 
   ✔ c92e735f0c1f Pull complete                                                                    14.3s 
   ✔ fa3c8c267e90 Pull complete                                                                    14.4s 
   ✔ d383da088699 Pull complete                                                                    25.0s 
   ✔ b838ac930a4c Pull complete                                                                    25.0s 
   ✔ 4f4fb700ef54 Pull complete                                                                    25.0s   

###Output from docker compose logs trilium
trilium  | No USER_UID specified, leaving 1000
trilium  | No USER_GID specified, leaving 1000
trilium  | (node:9) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
trilium  | (Use `node --trace-warnings ...` to show where the warning was created)
trilium  | DB size: 18878 KB
trilium  | Becca (note cache) load took 31ms
trilium  | Created option "locale" with default value "en"
trilium  | Created option "firstDayOfWeek" with default value "1"
trilium  | {
trilium  |   "appVersion": "0.90.6-beta",
trilium  |   "dbVersion": 228,
trilium  |   "nodeVersion": "v20.15.1",
trilium  |   "syncVersion": 32,
trilium  |   "buildDate": "2024-09-07T18:36:34Z",
trilium  |   "buildRevision": "7c0d6930fa8f20d269dcfbcbc8f636a25f6bb9a7",
trilium  |   "dataDirectory": "/home/node/trilium-data",
trilium  |   "clipperProtocolVersion": "1.0",
trilium  |   "utcDateTime": "2024-09-19T12:50:44.068Z"
trilium  | }
trilium  | CPU model: AMD Ryzen 7 7735U with Radeon Graphics, logical cores: 16, freq: 1329 Mhz
trilium  | Trusted reverse proxy: false
trilium  | App HTTP server starting up at port 8080
trilium  | Listening on port 8080
trilium  | 200 GET /api/health-check with 15 bytes took 6ms
trilium  | Table counts: notes: 769, revisions: 1380, attachments: 475, branches: 786, attributes: 856, etapi_tokens: 0, blobs: 1911
trilium  | All consistency checks passed with no errors detected (took 42ms)

[uniquegch]

Migration of Desktop Clients is also straigt forward.

for Arch I just run the command
yay -S triliumnext-bin ### https://aur.archlinux.org/packages/triliumnext-bin

for Debian I do the following steps:

1. sudo apt remove trilium
2. open a webbrowser and go to Trilium Next release page copy the link of the deb package
3. change to your directory for storing downloaded pacakags or tar or tar.gz etc ### I use ~/Downloads
4. cd Downloads

5.  wget https://github.com/TriliumNext/Notes/releases/download/v0.90.4/trilium_0.90.4_amd64.deb
6.  sudo dpkg -i trilium_0.62.6_amd64.deb   ### all depencendies are installed already from Zadam/Trilium

7. sudo apt install ./trilium_0.90.4_amd64.deb ### in case of clean installation or dpkg throughs errors regarding dependencies

Also if it is a clean install you will have to go through the inital setup as client conneting to a server

[DavidN78]

No traps?
I hit a complete roadblock since Trilium hadn't been updated, so the database was out of date. Logs had "App db version is 228, while db version is 215. Migration needed." and "ERROR: migration failed, crashing hard."
Solution was to update trilium first - in UnRAID, that meant editing the docker entry to zadam/trilium:0.63.7 (Advanced view).

[meichthys]

Noted. It is assumed that you would be on the latest version of Trilium before migrating to TriliumNext. That being said, I've added a note about upgrading to the latest Trilium version before migrating: https://github.com/TriliumNext/Notes/blob/develop/README.md#migrating-from-trilium

[DavidN78]

Indeed... and that does seem like a reasonable assumption.
In UnRAID there's a 'community apps' mechanism with point-n-click forms for Plugins and Docker images. (Very useful for newb's like me.) It's that mechanism for Trilium that hadn't been told there are updates.

[meichthys]

Makes sense 👍

[eliandoran]

@DavidN78 , anyway it's a good point you have raised, I'll look into the migration scripts since we might have accidentally broken something.