Wrong binary on a arm64 container

[jordiprats]

Hi,
Looks like you are mixing binaries from different architectures:

kubectl logs datadog-sv8dk -n datadog -c init-volume
standard_init_linux.go:211: exec user process caused "exec format error"

Appears to be the same as in 6037 but it is related to the initcontainer init-volume which is just using a cp launching a bash:

  initContainers:
  - args:
    - cp -r /etc/datadog-agent /opt
    command:
    - bash
    - -c
    image: gcr.io/datadoghq/agent-arm64:7.26.0
    imagePullPolicy: Always
    name: init-volume

[L3n41c]

Hello @jordiprats,

Thanks for reporting this issue!

Could you please share the output of kubectl describe node <NODE> where <NODE> is the node where this datadog-sv8dk pod is scheduled ?

I’m also seeing that you are trying to use the arch-specific image gcr.io/datadoghq/agent-arm64:7.26.0 instead of our multi-arch image gcr.io/datadoghq/agent:7.26.0 (see the -arm64 suffix).
Is there any specific reason for that ?
Our recommendation would be to use our multi-arch gcr.io/datadoghq/agent:7.26.0 image and let the CRI pull the correct image.