Skip to content

fix(loki): update config for Loki 3.x compatibility - #292

Merged
apham0001 merged 1 commit into
mainfrom
fix/loki-3x-config
Mar 12, 2026
Merged

fix(loki): update config for Loki 3.x compatibility#292
apham0001 merged 1 commit into
mainfrom
fix/loki-3x-config

Conversation

@apham0001

Copy link
Copy Markdown

Summary

  • Update loki/loki.yml from Loki 2.x to 3.x config format
  • Remove 3 deprecated/removed fields: max_transfer_retries, enforce_metric_name, max_look_back_period
  • Switch from boltdb/v11 to tsdb/v13 schema
  • Add common block with filesystem storage and inmemory ring
  • Add compactor with retention support
  • Update compose volume paths from /opt/loki to /loki (Loki 3.x container runs as non-root UID 10001)

Closes the config incompatibility reported when upgrading from LOKI_VERSION=2.9.17 to the default 3.6.7.

Test plan

  • Tested locally on charon-distributed-validator-node: Loki 3.6.7 starts successfully
  • Log push and query verified working
  • docker compose up full stack test

Loki config was written for 2.x and fails on 3.6.7 with:
- max_transfer_retries: removed in 3.0
- enforce_metric_name: removed in 3.0
- max_look_back_period: removed in 3.0

Updated to Loki 3.x config: tsdb store, v13 schema, common
block, compactor for retention. Volume path changed from
/opt/loki to /loki (3.x runs as non-root UID 10001).
@apham0001
apham0001 merged commit a5551a1 into main Mar 12, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants