![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/1f910de9-62b5-43a9-8c93-94821c945577.png)
Thanks, good point. Didn’t know about that risk
Thanks, good point. Didn’t know about that risk
Here is what I’m using atm. Is there a better way to do this? I’m still learning K8S :)
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: sonarr-pvc
spec:
accessModes:
- ReadWriteOnce
storageClassName: longhorn
resources:
requests:
storage: 250Mi
---
[....]
volumes:
- name: config
persistentVolumeClaim:
claimName: sonarr-pvc
Yeah I’m using Longhorn. Might be that I have set it up wrong, but didn’t seem to have helped with the DB corruption issue.
Basically this. I have my home stuff running in a K3S cluster, and I had to restore my Sonarr volume several times because the SQLite DB has corrupted. Transitioning to Postgres should solve this issue, and I already have quite a few other stuff in it, for example Radarr and Prowlarr
I got the same Obsidian+Syncthing setup atm, just haven’t really tried to use it for writing yet. Wanted to see what else others use that may trump it :)
No error logs, based on the logs tho it just ignores the config and uses the filesystem. So predictably once my small config mount fills up (this was before emptyDir), it starts to error out saying no more space on disk. Seemingly this didn’t cause any errors for Lemmy, still it doesn’t feel right :)
Will try this, thanks for the tip