Open qdupuy opened 3 years ago
Ran into the same issue. Looks like a missing volume mapping / mount point. This can be fixed with the following configuration for example:
tableManager:
enabled: true
replicas: 1
extraVolumes:
- name: bolt-db
emptyDir: {}
extraVolumeMounts:
- name: bolt-db
mountPath: /var/loki
hi, got the same problem. as soon as i have in storage config:
filesystem:
directory: /var/loki/chunks
i get this error.
I just ran into this same issue deploying the loki-distributed
chart with local / boltdb-shipper storage.
In my case the querier pod was failing with this same error:
msg="error running loki" err="mkdir /var/loki: read-only file system
Thanks to @DaveOHenry I was able to add the extra volume mounts to my values overrides:
querier:
replicas: 1
persistence:
# -- Enable creating PVCs for the querier cache
enabled: true
# -- Size of persistent disk
size: 10Gi
# -- Storage class to be used.
# If defined, storageClassName: <storageClass>.
# If set to "-", storageClassName: "", which disables dynamic provisioning.
# If empty or set to null, no storageClassName spec is
# set, choosing the default provisioner (gp2 on AWS, standard on GKE, AWS, and OpenStack).
storageClass: null
extraVolumes:
- name: bolt-db
emptyDir: {}
extraVolumeMounts:
- name: bolt-db
mountPath: /var/loki
This was fixed by https://github.com/grafana/helm-charts/pull/1347. This issue can now be closed.
Issue not fixed.
@qdupuy Try latest version helm chart
experiencing the same with 5.8.0 grafana/loki chart
Hello 🖖
when I try to deploy table-manager I get the following error :
Here is my loki config file :
Using loki-distributed helm charts.
loki image : docker.io/grafana/loki:2.3.0
Did I miss something on the helm charts?