<p>Yes, mongodb 5 on x86 requires a cpu with avx, check your cpu flags of the kubernetes node with lscpu | grep avx</p>

CC BY-SA 4.0
2023-11-28T10:01:40.803Z
mongodb should check that and emit a proper error
Serve Laurijssen
CC BY-SA 4.0
2023-11-28T08:45:50.890Z
2023-11-28T08:45:50.890Z
Juzar
<p>Here is my <code>My Chart.yaml</code> file:</p>
<pre class="lang-yaml prettyprint-override"><code>apiVersion: v2
name: pixer-microservice-infra
description: A Helm chart for Kubernetes
type: application
version: 0.1.0
appVersion: &quot;1.16.0&quot;
dependencies:
  - name: mongodb
    version: ~14.3.1
    repository: &quot;@bitnami&quot;
    alias: mongodb
</code></pre>
<p>After running commands:</p>
<pre><code>helm dependency build .
helm upgrade &lt;chart-name&gt;
</code></pre>
<p>my mongodb pod has the status: CrashLoopBackOff</p>
<p>Checked pod logs: <code>kubectl logs pod/&lt;pod-name&gt;</code></p>
<p><code>/opt/bitnami/scripts/libos.sh: line 346:   154 Illegal instruction     &quot;$@&quot; &gt; /dev/null 2&gt;&amp;1</code></p>
<p><code>uname -m</code>: arm64</p>
<p>Is there any compatible issue between this chart and the CPU architecture?</p>

<kubernetes><helm><kubernetes-helm>
helm trouble creating pod using bitnami/mongodb chart
harrydang
# helm trouble creating pod using bitnami/mongodb chart

(Asked by: username_0 on 2023-11-27)

Here is my My Chart.yaml file:
apiVersion: v2
name: pixer-microservice-infra
description: A Helm chart for Kubernetes
type: application
version: 0.1.0
appVersion: "1.16.0"
dependencies:
  - name: mongodb
    version: ~14.3.1
    repository: "@bitnami"
    alias: mongodb

After running commands:
helm dependency build .
helm upgrade 

my mongodb pod has the status: CrashLoopBackOff
Checked pod logs: kubectl logs pod/
/opt/bitnami/scripts/libos.sh: line 346:   154 Illegal instruction     "$@" > /dev/null 2>&1
uname -m: arm64
Is there any compatible issue between this chart and the CPU architecture?

**Tags:** kubernetes, helm, kubernetes-helm


---

## 1 answers

### Answer by username_1 on 2023-11-28. Score: 1

Yes, mongodb 5 on x86 requires a cpu with avx, check your cpu flags of the kubernetes node with lscpu | grep avx

> **Comments:**
> **username_2**: mongodb should check that and emit a proper error  

---

