# Oneagent - Dynakube deployment fails for K8s arm64 nodes

**URL:** <https://community.dynatrace.com/t/oneagent-dynakube-deployment-fails-for-k8s-arm64-nodes/45369>\
**Category:** Container platforms\
**Tags:** oneagent, kubernetes\
**Created:** [April 30, 2024, 2:02pm UTC](https://community.dynatrace.com/t/oneagent-dynakube-deployment-fails-for-k8s-arm64-nodes/45369 "2024-04-30T14:02:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![amr\_1509](https://avatars.discourse-cdn.com/v4/letter/a/67e7ee/32.png) [@amr\_1509](https://community.dynatrace.com/u/amr_1509)\
**Post date:** [April 30, 2024, 2:02pm UTC](https://community.dynatrace.com/t/oneagent-dynakube-deployment-fails-for-k8s-arm64-nodes/45369/1 "2024-04-30T14:02:15Z")

</div>

I am trying to deploy dynakube for arm64 nodes and i am getting the below error:

```markup
[2024-04-30 10:58:10.427 UTC] [0004cfb7] [info] [bootstrapper] Started agent deployment as a container, PID 315319
[2024-04-30 10:58:10.427 UTC] [0004cfb7] [error] [bootstrapper] Read-only mode is supported only with volume-based storage

```

Can someone provide some insights to fix this?

But the same configuration works just fine for amd64 nodes. I am using the image tailored for arm64 nodes. Here is my dynakube config:

```markup
apiVersion: dynatrace.com/v1beta1
kind: DynaKube
metadata:
  name: oa-arm
  namespace: dynatrace
  annotations:
    feature.dynatrace.com/automatic-kubernetes-api-monitoring: "true"
    feature.dynatrace.com/oneagent-readonly-host-fs: "false"
    feature.dynatrace.com/automatic-injection: "false"

spec:
  apiUrl: https://{environmentid}.live.dynatrace.com/api
  tokens: "XXXXXXX"
  skipCertCheck: false
  namespaceSelector:
    matchLabels:
      dynatrace.com/inject: "true"
  oneAgent:
    cloudNativeFullStack:
      image: "dynatrace/dynatrace-oneagent:1.277.204.20231129-185056"
      version: ""
      initResources: {}
      nodeSelector:
        kubernetes.io/arch: arm64
      tolerations:
        - effect: NoSchedule
          key: node-role.kubernetes.io/master
          operator: Exists
        - effect: NoSchedule
          key: node-role.kubernetes.io/control-plane
          operator: Exists
      oneAgentResources: {}
      args:
        - --set-monitoring-mode=fullstack
        - --set-host-group=oa-arm
      env:
        - name: ONEAGENT_ENABLE_VOLUME_STORAGE
          value: "false"
      autoUpdate: true
      priorityClassName: ""
      dnsPolicy: ""
      labels: {}

```

---

<div class="post-metadata">

**Author:** ![cyanogen](https://avatars.discourse-cdn.com/v4/letter/c/9f8e36/32.png) [@cyanogen](https://community.dynatrace.com/u/cyanogen)\
**Post date:** [June 20, 2024, 5:53am UTC](https://community.dynatrace.com/t/oneagent-dynakube-deployment-fails-for-k8s-arm64-nodes/45369/2 "2024-06-20T05:53:04Z")

</div>

We got same issue with ARM64 arch ocp

Please help

---

<div class="post-metadata">

**Author:** ![gopher](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/gopher/32/5728_2.png) [@gopher](https://community.dynatrace.com/u/gopher)\
**Post date:** [June 20, 2024, 6:48am UTC](https://community.dynatrace.com/t/oneagent-dynakube-deployment-fails-for-k8s-arm64-nodes/45369/3 "2024-06-20T06:48:58Z")

</div>

Hi AMR / Cyanogen,

looks like a config issue around your storage type.&nbsp;  
probably related to the feature & setting environment

```auto
ONEAGENT_ENABLE_VOLUME_STORAGE

```

cloud native full stack uses CSI compared to One Agent.  
Perhaps try flipping back to default config and see how you go.  
[dynatrace-operator/assets/samples/dynakube/v1beta2/cloudNativeFullStack.yaml at main · Dynatrace/dynatrace-operator · GitHub](https://github.com/Dynatrace/dynatrace-operator/blob/main/assets/samples/dynakube/v1beta2/cloudNativeFullStack.yaml)

Also make sure that you have the correct image type

 ![Peter_Ralston_0-1718866037638.png](https://global.discourse-cdn.com/dynatrace/original/2X/1/1c74c492d50185bfa329dd145bd167aac4cbd2d1.png)

Good luck
