BeardLord

I'm just using the original mounts from the template: /etc/loki -> /mnt/user/appdata/loki/conf/ This is where my local-config.yaml file lives. /loki -> /mnt/user/appdata/loki/ This where Loki stores all of its data. I just checked, and it's ~26GB for ~90 days of logs. I'll probably play around with the compactor settings, or move it out of my appdata share eventually. I just checked my own instance of Loki, and it looks like it's on the latest version, and running fine with the above config. ~ $ loki --version loki, version 3.5.7 (branch: release-3.5.x, revision: d5b382b9) build user: root@buildkitsandbox build date: 2025-10-13T08:58:08Z go version: go1.24.8 platform: linux/amd64 tags: netgoWhat kind of error are you getting?

I added the following line to `/boot/config/docker.cfg`, and restarted the docker daemon with `/etc/rc.d/rc.docker restart`. DOCKER_OPTS="--log-driver=loki --log-opt loki-url=http://localhost:3100/loki/api/v1/push --log-opt loki-batch-size=400" and confirmed the setting was picked up using this: $ ps aux | grep -i /usr/bin/dockerd root ... /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50m --log-opt max-file=1 --log-level=fatal --log-driver=loki --log-opt loki-url=http://localhost:3100/loki/api/v1/push --log-opt loki-batch-size=400 --storage-driver=btrfs I don't know if `DOCKER_OPTS` will survive reboots though. I found logs in Grafana for some containers, but not others, but then found the container needs to be recreated (i.e. not just restarted) for the log-driver to changed. Does anyone know of a nice way of doing this? (I'm too lazy to do it container by container myself, so hoping regular container updates will do it 😂). You can see the currently configured log-driver per container using this: docker inspect <ContainerName> | jq '.[].HostConfig.LogConfig'

Hi all, I spent some time working on this today, and think I have a config that works with the latest version of Loki. It's mostly copied from: https://grafana.com/docs/loki/latest/configure/examples/configuration-examples/#1-local-configuration-exampleyaml with some small changes to the paths to make sure they are on a share, and not within the containers filesystem. I can confirm the container is working out of the box with this config, and logs are showing up in Grafana. auth_enabled: false server: http_listen_port: 3100 common: ring: instance_addr: 127.0.0.1 kvstore: store: inmemory replication_factor: 1 path_prefix: /loki schema_config: configs: - from: 2020-05-15 store: tsdb object_store: filesystem schema: v13 index: prefix: index_ period: 24h storage_config: filesystem: directory: /loki/chunks I've also created a PR to update the example `local_config.yaml` file that's linked in the template description: https://github.com/natcoso9955/unRAID-docker/pull/7 I haven't looked into changing anything else from default, but feel free to drop a comment on the PR if you know of any UnRAID specific optimisations.

I have an older backup from around August last year, but I don't think I would have changed the disk setup since then tbh. I've been between two houses, and the server was mostly powered off for that time. Should I restore the backups fully, or just the individual files? Edit: I tried restoring only the corrupted files, via making the flash public and copying them over, and then rebooting. It removed the error message, but now I noticed that the AppData share is empty, and the cache drive was unmounted. I've copied over the cache config now, and rebooting again. I have the CA Backup plugin, but not 100% it will restore everything. Edit #2: Oh wow, the AppData share was empty because it all lived on the cache drive, so it all reappeared after the above reboot I think I'm back in action now, so probably a good time to make all the backups.

Hi all, I have moved my media server between houses, and then recieved the following error: "Your flash drive is corrupted or offline. Post your diagnostics in the forum for help. See also here". In case it helps, Fix Common Errors says: ``` /boot/config/disk.cfg corrupted /boot/config/plugins/dynamix/monitor.ini corrupted ``` I havn't started the Array yet since moving, for fear of corrupting something else. Thanks tower-diagnostics-20230716-1949.zip