December 21, 20241 yr I recently tried using this unRAID template. First, I hit permission errors on the /loki WAL during initial startup. Noticed the image was 2 years old and changed it to the "latest" tag and re-pulled. Now during initial startup, I hit a few deprecated parameters from the local-config.yaml file suggested in the https://github.com/natcoso9955/unRAID-docker/blob/master/configs/loki/local-config.yaml file. failed parsing config: /etc/loki/local-config.yaml: yaml: unmarshal errors: line 18: field max_transfer_retries not found in type ingester.Config line 38: field enforce_metric_name not found in type validation.plain line 43: field max_look_back_period not found in type config.ChunkStoreConfig. Use `-config.expand-env=true` flag if you want to expand environment variables in your config file I researched each one and remediated. Now I'm hitting a schema validation error that says I am using schema v11 and need to upgrade to v13 and then several other field issues. With over 1,000,000,000 downloads on this, I feel like this is a me problem. Whats the best way forward to get a new setup rolling?
December 27, 20241 yr On 12/21/2024 at 12:13 PM, birdsofprey02 said: I recently tried using this unRAID template. First, I hit permission errors on the /loki WAL during initial startup. Noticed the image was 2 years old and changed it to the "latest" tag and re-pulled. Now during initial startup, I hit a few deprecated parameters from the local-config.yaml file suggested in the https://github.com/natcoso9955/unRAID-docker/blob/master/configs/loki/local-config.yaml file. failed parsing config: /etc/loki/local-config.yaml: yaml: unmarshal errors: line 18: field max_transfer_retries not found in type ingester.Config line 38: field enforce_metric_name not found in type validation.plain line 43: field max_look_back_period not found in type config.ChunkStoreConfig. Use `-config.expand-env=true` flag if you want to expand environment variables in your config file I researched each one and remediated. Now I'm hitting a schema validation error that says I am using schema v11 and need to upgrade to v13 and then several other field issues. With over 1,000,000,000 downloads on this, I feel like this is a me problem. Whats the best way forward to get a new setup rolling? I too am also facing the same issue. Since the template on github was last updated 2 years ago, my guess is that the config is outdated as well. I lack knowledge in this, so hoping someone could help.
January 3, 20251 yr On 12/20/2024 at 11:13 PM, birdsofprey02 said: I recently tried using this unRAID template. First, I hit permission errors on the /loki WAL during initial startup. Noticed the image was 2 years old and changed it to the "latest" tag and re-pulled. Now during initial startup, I hit a few deprecated parameters from the local-config.yaml file suggested in the https://github.com/natcoso9955/unRAID-docker/blob/master/configs/loki/local-config.yaml file. failed parsing config: /etc/loki/local-config.yaml: yaml: unmarshal errors: line 18: field max_transfer_retries not found in type ingester.Config line 38: field enforce_metric_name not found in type validation.plain line 43: field max_look_back_period not found in type config.ChunkStoreConfig. Use `-config.expand-env=true` flag if you want to expand environment variables in your config file I researched each one and remediated. Now I'm hitting a schema validation error that says I am using schema v11 and need to upgrade to v13 and then several other field issues. With over 1,000,000,000 downloads on this, I feel like this is a me problem. Whats the best way forward to get a new setup rolling? Honestly facing the same issues. That being said, I tried a different template (the one by McJoppy: and it does work. That being said, I was looking at wanting to customizing the promtail.yaml file, and can't figure out how to get that done. I'm really hoping someone will be able to help us out.
February 2, 20251 yr 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.
February 26, 20251 yr On 2/1/2025 at 4:46 PM, BeardLord said: 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. Thank you! Would you mind clarifying what you mean make sure the config is on a share? If it's on a share how would I direct the container to use it? Any additional details you can provide would be helpful. Thank you!
May 16, 20251 yr On 2/1/2025 at 7:46 PM, BeardLord said: 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. any guidance you can offer on getting this working with current versions?
October 17, 2025Oct 17 On 2/26/2025 at 5:19 AM, physikal said:Thank you! Would you mind clarifying what you mean make sure the config is on a share? If it's on a share how would I direct the container to use it? Any additional details you can provide would be helpful. Thank you!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.On 5/17/2025 at 12:16 AM, dnoyeb said:any guidance you can offer on getting this working with current versions?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?
October 22, 2025Oct 22 On 10/17/2025 at 3:00 PM, BeardLord said: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'm not OP but I tried setting this up today. I get the following error when using that config:2025-10-22 01:45:03.157932 I | proto: duplicate proto type registered: purgeplan.DeletePlan 2025-10-22 01:45:03.158083 I | proto: duplicate proto type registered: purgeplan.ChunksGroup 2025-10-22 01:45:03.158097 I | proto: duplicate proto type registered: purgeplan.ChunkDetails 2025-10-22 01:45:03.158112 I | proto: duplicate proto type registered: purgeplan.Interval 2025-10-22 01:45:03.173177 I | proto: duplicate proto type registered: grpc.PutChunksRequest 2025-10-22 01:45:03.173199 I | proto: duplicate proto type registered: grpc.GetChunksRequest 2025-10-22 01:45:03.173211 I | proto: duplicate proto type registered: grpc.GetChunksResponse 2025-10-22 01:45:03.173223 I | proto: duplicate proto type registered: grpc.Chunk 2025-10-22 01:45:03.173236 I | proto: duplicate proto type registered: grpc.ChunkID 2025-10-22 01:45:03.173251 I | proto: duplicate proto type registered: grpc.DeleteTableRequest 2025-10-22 01:45:03.173266 I | proto: duplicate proto type registered: grpc.DescribeTableRequest 2025-10-22 01:45:03.173278 I | proto: duplicate proto type registered: grpc.WriteBatch 2025-10-22 01:45:03.173291 I | proto: duplicate proto type registered: grpc.WriteIndexRequest 2025-10-22 01:45:03.173303 I | proto: duplicate proto type registered: grpc.DeleteIndexRequest 2025-10-22 01:45:03.173314 I | proto: duplicate proto type registered: grpc.QueryIndexResponse 2025-10-22 01:45:03.173327 I | proto: duplicate proto type registered: grpc.Row 2025-10-22 01:45:03.173340 I | proto: duplicate proto type registered: grpc.IndexEntry 2025-10-22 01:45:03.173354 I | proto: duplicate proto type registered: grpc.QueryIndexRequest 2025-10-22 01:45:03.173368 I | proto: duplicate proto type registered: grpc.UpdateTableRequest 2025-10-22 01:45:03.173387 I | proto: duplicate proto type registered: grpc.DescribeTableResponse 2025-10-22 01:45:03.173400 I | proto: duplicate proto type registered: grpc.CreateTableRequest 2025-10-22 01:45:03.173415 I | proto: duplicate proto type registered: grpc.TableDesc 2025-10-22 01:45:03.173431 I | proto: duplicate proto type registered: grpc.TableDesc.TagsEntry 2025-10-22 01:45:03.173451 I | proto: duplicate proto type registered: grpc.ListTablesResponse 2025-10-22 01:45:03.173469 I | proto: duplicate proto type registered: grpc.Labels 2025-10-22 01:45:03.173707 I | proto: duplicate proto type registered: storage.Entry 2025-10-22 01:45:03.173734 I | proto: duplicate proto type registered: storage.ReadBatch failed parsing config: /etc/loki/local-config.yaml: yaml: unmarshal errors: line 11: field replication_factor not found in type common.ConfigI tried commenting out replication_factor and it gives the followinglevel=error ts=2025-10-22T01:47:19.57344859Z caller=main.go:51 msg="validating config" err="invalid schema config: invalid schema version"
November 3, 2025Nov 3 On 10/31/2025 at 5:36 PM, MonkeyAdminOnKeyboard said:i got the same error field replication_factor not found in type common.ConfigI can confirm im getting the same thing, which is weird because this is pretty much the example on the grafana loki page at Configuration | Grafana Loki documentation
November 10, 2025Nov 10 Spent some time sorting this today. This is what I did & my setttings:Change Repository to grafana/loki:latest Using this local-config.yaml Check version by running "loki --version" via loki console(Result is I'm running latest version!) Enjoy! local-config.yaml Edited November 10, 2025Nov 10 by paladin Add yaml
November 11, 2025Nov 11 On 11/3/2025 at 11:39 AM, SirNugg3ts said:I can confirm im getting the same thing, which is weird because this is pretty much the example on the grafana loki page at Configuration | Grafana Loki documentationOn 10/31/2025 at 5:36 PM, MonkeyAdminOnKeyboard said:i got the same error field replication_factor not found in type common.ConfigI had this too but managed to get it up and running from a tip from Paladin above, Just updated the repository to use the :latest tag, and then used the same config from the docs page:https://grafana.com/docs/loki/latest/configure/examples/configuration-examples/#1-local-configuration-exampleyamlNow it's running and I've got Grafana connected to it
February 10Feb 10 On 11/19/2025 at 6:17 PM, isp1337 said:They switched from master to maina couple of years ago it seems.This worked for me. Switching to main then using the default local-config.yaml here.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.