RISC-V Docker image - unofficial build that works around riscv64 blockers

[12345qwert123456]

Hey everyone,

I've been running TriliumNext on an OrangePi RV2 and wanted to share a working Dockerfile for linux/riscv64, since the official image doesn't publish a riscv64 manifest.

Built and tested against TriliumNext v0.102.1, also runs fine under QEMU riscv64 on a regular x86-64 machine - so anyone can try it without physical hardware.

Why a straight cross-build fails on riscv64

There are three blockers I ran into:

1. No official node:*-alpine image for riscv64 - Alpine's own nodejs package is used instead
2. The frontend build (Vite/Rollup + CKEditor) crashes with a V8 kMaxBranchOffset out-of-range error on riscv64; lightningcss also has no prebuilt binary for this arch
3. better-sqlite3 has no prebuilt binary for node-v127-linux-riscv64 and must be compiled from source via node-gyp

How the Dockerfile solves this

The build is split into stages:

• The backend (TypeScript - main.cjs via esbuild, which ships a prebuilt riscv64 binary) and better-sqlite3 are compiled natively on riscv64
• The frontend (public/, pdfjs-viewer/, share-theme/) is copied from the official AMD64 image using COPY --from no RUN commands, so Docker never executes AMD64 code and QEMU is not required at build time for this stage

The result is a minimal Alpine image that runs the server natively on riscv64.

Proof of works

Repo & Docker Hub

GitHub: https://github.com/12345qwert123456/Trilium.RISC-V
Docker Hub: https://hub.docker.com/r/12345qwert123456/trilium-riscv64

The repo includes a GitHub Actions workflow that automatically tracks new stable TriliumNext releases and rebuilds the image.

Happy to turn this into a PR if there's interest in adding riscv64 to the official image build matrix. The main question would be where the frontend layers should come from in a fully integrated CI pipeline - open to suggestions.