2 years ago
I am trying to reproduce the problem on my side why it is erroring out, even though I have the volume mounted for persistence.
For context, here's the logs:
2024/06/03 18:55:23 NewSQLiteDB("/home/nonroot/golink.db"): unable to open database file: out of memory (14)
How to reprod
Create a service using
ghcr.io/tailscale/golink:mainimage.Set
TS_AUTHKEYinto your own Tailscale authkey from the admin dashboard.Mount volume to
/home/nonrootand start.
ⓘ Deployment information is only viewable by project members and Railway employees.
2 Replies
2 years ago
Volumes are mounted as root, so you would need to also run the application as root, you can try setting a service variable `RAILWAY_RUN_UID` to `0` but that nonroot directory does not give me confidence that the variable will work.
2 years ago
Volumes are mounted as root, so you would need to also run the application as root, you can try setting a service variable `RAILWAY_RUN_UID` to `0` but that nonroot directory does not give me confidence that the variable will work.
@brody maybe I could use the aforementioned image as a base image to fix permission chaos (chmoding I guess) or just change the -sqlitedb flag value, but I'll try using RUN_UID first
Status changed to Solved brody • about 1 year ago