TriliumNext on kubernetes. Will not start. Error

[HomeLabJunkie]

As stated it just will not start

usermod: no changes │
│ node:fs:1364 │
│ const result = binding.mkdir( │
│ ^ │
│ │
│ Error: EACCES: permission denied, mkdir '/trilium-data/log' │
│ at Object.mkdirSync (node:fs:1364:26) │
│ at file:///usr/src/app/src/services/log.js:7:8 │
│ at ModuleJob.run (node:internal/modules/esm/module_job:271:25) │
│ at async onImport.tracePromise.proto (node:internal/modules/esm/loader:547:26) │
│ at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:116:5) { │
│ errno: -13, │
│ code: 'EACCES', │
│ syscall: 'mkdir', │
│ path: '/trilium-data/log' │
│ } │
│ │
│ Node.js v22.13.1

[HomeLabJunkie]

Have also tried with different pod security options

defaultPodOptions:
  securityContext:
    runAsNonRoot: true
    runAsUser: 1000
    runAsGroup: 1000
    fsGroup: 1000
    fsGroupChangePolicy: OnRootMismatch
    seccompProfile: { type: RuntimeDefault }

[perfectra1n]

Can you share your entire manifest @HomeLabJunkie? Including the Release and PVC.

edit: nvm found it https://github.com/HomeLabJunkie/k8s-cluster/blob/8a76846aa392eb9eb4a7177ea78fe73d5915e72b/kubernetes/apps/default/trilium/app/helmrelease.yaml#L59

[perfectra1n]

It looks like you're using 0nedrop's cluster template, oddly enough we're even leveraging the app-template for our Helm chart :)

Here's a link to our Release that we're using for our Helm chart:
https://github.com/TriliumNext/helm-charts/blob/d90e11f297bf52b9876d5bebc0b7fbf9c2cfe837/charts/trilium/templates/release.yaml#L66

And our values:
https://github.com/TriliumNext/helm-charts/blob/d90e11f297bf52b9876d5bebc0b7fbf9c2cfe837/charts/trilium/values.yaml#L1

But something is blocking Trilium from writing to your data directory in the PVC:

Error: EACCES: permission denied, mkdir '/trilium-data/log'

[perfectra1n]

Perhaps try changing your PVC mountpoint, instead of overriding the data directory environment variable:
https://github.com/TriliumNext/helm-charts/blob/d90e11f297bf52b9876d5bebc0b7fbf9c2cfe837/charts/trilium/templates/release.yaml#L55

[perfectra1n]

Here's the code that creates the log directory:

if (!fs.existsSync(dataDir.LOG_DIR)) {
    fs.mkdirSync(dataDir.LOG_DIR, 0o700);
}

So something is not allowing Trilium to create that directory. I've seen Longhorn be very weird with permissions, so some use initContainers (like our Helm chart does) to fix the permissions, which you can try as well. https://github.com/TriliumNext/helm-charts/blob/d90e11f297bf52b9876d5bebc0b7fbf9c2cfe837/charts/trilium/templates/release.yaml#L5

[perfectra1n]

It might be worth spinning up another container like Ubuntu (like in the Longhorn docs) to validate that Longhorn is actually changing the permissions on the folder that is being mounted via the PVC

[HomeLabJunkie]

I was not able to figure it out. No need to continue this thread so I'll close it.