Trilium Notes deployed to Google Cloud Run as Docker image resets after short period of inactivity

[januhlir]

Description

I recently deployed Trilian Next to the Google Cloud Run, as a Docker image, so I can use it from anywhere.
It seemed like a success, it worked for a while just after deployment. But when I reopened the site after a few days of not using it, instead of seeing my notes I was welcome with a Trilian setup screen again. It looks like data were wiped out. Luckily I didn't have anything important there. It was still just a test.

Anyone guess what might have caused the data loss?

I am using “Cloud Run” service.
https://cloud.google.com/run

Docker image used:
https://hub.docker.com/r/triliumnext/notes

Container configuration:
Container Image URL: docker.io/triliumnext/notes:v0.92.7
Port: ...
Volume Mount: espinosa-volume-1
Mount path: /espinosa/trilium-data

Volume configuration:
Volume type: Cloud Storage Type
Volume name: espinosa-volume-1
Bucket: espinosa-bucket-1

It runs on URL:
https://…...run.app

This is my first Docker deployment to cloud. I have little experience with any Google Cloud services.
I have no fronting server, like Nginx, Trillium endpoint is exposed directly.

TriliumNext Version

0.92.7

What operating system are you using?

Other Linux

What is your setup?

Local (no sync)

Operating System Version

Google Cloud Run

Error logs

No response

[januhlir]

I'm asking for help also here:
https://superuser.com/questions/1894694/trilium-notes-deployed-to-google-cloud-run-as-docker-image-resets-after-short-pe

[eliandoran]

Hi,

I can't help you directly since I've never used Google Cloud.

However, the issue you are having seems to be related to a wrong volume mount.

You mentioned:

Volume Mount: espinosa-volume-1
Mount path: /espinosa/trilium-data

Is this mount path inside the Docker container? If so, then it is incorrect.
After setting up Trilium you can check the data directory by going to the help section.

[januhlir]

You are absolutely right!
I changed Mount path to: /home/node/trilium-data
And it works now. I changed it couple of days ago and my notes are clearly permanently stored.
I even stopped the service, re-deployed, played with configuration (I'm trying to change port), redeployed again, service was down due to my attempts, fixed, redeployed - and my data are still there.

[perfectra1n]

Yeah I'm not sure if this actually related to Trilium. This seems to be a deployment configuration issue / error. Try running it in Docker locally. If it works via Docker locally, then your deployment via Google Cloud is the issue...

[JYC333]

If my memory is correct, "Cloud Run" is more like a function running service which doesn't support save data persistently somewhere. It' actually not the case for running Trilium server, you need to set up a VM which can have a persistent storage connected.

[januhlir]

I've fixed it. Trilian Docker image can definitively run as Google Run service. @eliandoran was right, my mount path was incorrect. It cannot be just anything, it must be /home/node/trilium-data.

"Cloud Run" is more like a function running

Yes, but you can pair it with other services, like permanent storage, like Google Cloud Storage (Buckets) or NFS (external storage provider). I use the Google Cloud Storage.

Also, you have to use another Google service: Google Artifact Registry. The is where the Docker image from Docker Hub was transparently pushed for me. If I would to create a modified Docker image, like paired Trilium + Nginx, I would built this image locally and pushed it directly to Google Artifact Registry.

All 3 services are billed separately. I hope to fit into free quota for Google Run and Google Artifact Registry, but Google Cloud Storage is probably where I will have to cough up the dough eventually.

[januhlir]

It's all working. Trilian Docker image can definitively run as Google Run service.
The issue was misconfigured Mount path.

I'm a bit puzzled how could Trilian even start with such misconfiguration.
Perhaps more checks could be done on server start?

Anyway, you can check if your Trilian persisted files in the Google Cloud Storage for yourself.
In Cloud Run console, open your Cloud Run project in edit mode, go to:
Volumes -> Edit Volume -> Bucket -> Browse
It opens a simple file manager where you see all files Trilian creates, like "document.db".