<p>Managed to solve this by changing the <code>values.yaml</code> in the <code>loki-stack</code> helm chart to the following:</p>
<pre><code>promtail:
  enabled: true
  pipelineStages:
  - cri: {}
</code></pre>
<p>Enjoy.</p>

CC BY-SA 4.0
2021-03-15T22:58:37.620Z
2021-03-15T22:58:37.620Z
user2324712
<p>I am trying to configure <a href="https://github.com/grafana/helm-charts/tree/main/charts/loki-stack" rel="nofollow noreferrer">loki-stack using a helm chart</a> to my k8s cluster.</p>
<p>Since my k8s cluster uses CRIO and not docker (which is common nowdays) I need to change the <code>pipeline_stages:</code> config map to use <a href="https://grafana.com/docs/loki/latest/clients/promtail/stages/cri/" rel="nofollow noreferrer"><code>cri: {}</code></a> instead of <code>docker: {}</code> to parse the logs properly.</p>
<p>How do I change the helm chart so that <code>cri: {}</code> is used by default instead of <code>docker: {}</code> in all the <code>pipeline_stages:</code>? many thanks.</p>

CC BY-SA 4.0
2021-03-15T10:45:59.217Z
Doesn't the most recent version of that chart already use cri by default? https://github.com/grafana/helm-charts/blob/22b248efd4171a649fdef881b3f0b3a756b90809/charts/promtail/values.yaml#L239
Briansbum
CC BY-SA 4.0
2021-03-15T19:51:45.717Z
for some reason when i deploy the loki-stack helm chart, it deploys it with docker... I did actually try in my requirements.yaml to require the latest version by doing `version: "^3.5.0"` for promtail and it keeps deploying docker :(
user2324712
CC BY-SA 4.0
2021-03-15T20:05:55.417Z
@Briansbum, per your comment, i've attempted to deploy loki-stack in a katacoda k8s cluster independently of my own cluster and I can confirm that it used `docker: {}` instead of `cri: {}` as well. I think that the helm chart has a snippet using cri but is not actually using it and something needs to be done to make it use `cri: {}` instead of `docker: {}`
user2324712
<kubernetes><helm><logging><grafana><kubernetes-helm>
How to deploy loki-stack helm chart with CRIO?
user2324712
# How to deploy loki-stack helm chart with CRIO?

(Asked by: username_0 on 2021-03-14)

I am trying to configure [loki-stack using a helm chart](https://github.com/grafana/helm-charts/tree/main/charts/loki-stack) to my k8s cluster.

Since my k8s cluster uses CRIO and not docker (which is common nowdays) I need to change the `pipeline_stages:` config map to use [`cri: {}`](https://grafana.com/docs/loki/latest/clients/promtail/stages/cri/) instead of `docker: {}` to parse the logs properly.

How do I change the helm chart so that `cri: {}` is used by default instead of `docker: {}` in all the `pipeline_stages:`? many thanks.

**Tags:** kubernetes, helm, logging, grafana, kubernetes-helm

> **Comments:**
> **username_1**: Doesn't the most recent version of that chart already use cri by default? https://github.com/grafana/helm-charts/blob/22b248efd4171a649fdef881b3f0b3a756b90809/charts/promtail/values.yaml#L239  
> **username_0**: for some reason when i deploy the loki-stack helm chart, it deploys it with docker... I did actually try in my requirements.yaml to require the latest version by doing `version: "^3.5.0"` for promtail and it keeps deploying docker :(  
> **username_0**: @username_1, per your comment, i've attempted to deploy loki-stack in a katacoda k8s cluster independently of my own cluster and I can confirm that it used `docker: {}` instead of `cri: {}` as well. I think that the helm chart has a snippet using cri but is not actually using it and something needs to be done to make it use `cri: {}` instead of `docker: {}`  

---

## 1 answers

### Answer by username_0 on 2021-03-15. Score: 1 | Accepted answer

Managed to solve this by changing the values.yaml in the loki-stack helm chart to the following:
promtail:
  enabled: true
  pipelineStages:
  - cri: {}

Enjoy.


---

