-
Notifications
You must be signed in to change notification settings - Fork 205
Description
I have read the article of wazuh 4.12.0 which stated that it will support the arm64 CPU architecture as well, but even after following the exact step in Documentation, I am getting below error
ubuntu@ip-10-0-86-183:~/wazuh/wazuh-kubernetes$ kubectl get pods -n wazuh NAME READY STATUS RESTARTS AGE wazuh-dashboard-7459d4cc48-8xs4p 0/1 Error 3 (40s ago) 55s wazuh-indexer-0 0/1 Error 3 (29s ago) 55s wazuh-indexer-1 0/1 CrashLoopBackOff 1 (15s ago) 29s wazuh-manager-master-0 0/1 Error 3 (31s ago) 55s wazuh-manager-worker-0 0/1 Error 3 (31s ago) 55s wazuh-manager-worker-1 0/1 Error 3 (30s ago) 55s **ubuntu@ip-10-0-86-183:~/wazuh/wazuh-kubernetes$ kubectl logs wazuh-dashboard-7459d4cc48-8xs4p -n wazuh exec /entrypoint.sh: exec format error** ubuntu@ip-10-0-86-183:~/wazuh/wazuh-kubernetes$ kubectl get nodes --show-labels | grep arm64 ip-10-0-34-189.ec2.internal Ready <none> 176d v1.31.3-eks-7636447 beta.kubernetes.io/arch=arm64,beta.kubernetes.io/instance-type=t4g.2xlarge,beta.kubernetes.io/os=linux,eks.amazonaws.com/capacityType=ON_DEMAND,eks.amazonaws.com/nodegroup-image=ami-0b5065637f133c249,eks.amazonaws.com/nodegroup=ng-3-staging-eksworkers-arm,failure-domain.beta.kubernetes.io/region=us-east-1,failure-domain.beta.kubernetes.io/zone=us-east-1c,k8s.io/cloud-provider-aws=a0b51d2ff99041a747197fd1822b7300,kubernetes.io/arch=arm64,kubernetes.io/hostname=ip-10-0-34-189.ec2.internal,kubernetes.io/os=linux,node.kubernetes.io/instance-type=t4g.2xlarge,topology.ebs.csi.aws.com/zone=us-east-1c,topology.k8s.aws/zone-id=use1-az1,topology.kubernetes.io/region=us-east-1,topology.kubernetes.io/zone=us-east-1c ip-10-0-84-142.ec2.internal Ready <none> 187d v1.31.3-eks-7636447 beta.kubernetes.io/arch=arm64,beta.kubernetes.io/instance-type=t4g.2xlarge,beta.kubernetes.io/os=linux,eks.amazonaws.com/capacityType=ON_DEMAND,eks.amazonaws.com/nodegroup-image=ami-0b5065637f133c249,eks.amazonaws.com/nodegroup=ng-3-staging-eksworkers-arm,failure-domain.beta.kubernetes.io/region=us-east-1,failure-domain.beta.kubernetes.io/zone=us-east-1f,k8s.io/cloud-provider-aws=a0b51d2ff99041a747197fd1822b7300,kubernetes.io/arch=arm64,kubernetes.io/hostname=ip-10-0-84-142.ec2.internal,kubernetes.io/os=linux,node.kubernetes.io/instance-type=t4g.2xlarge,topology.ebs.csi.aws.com/zone=us-east-1f,topology.k8s.aws/zone-id=use1-az5,topology.kubernetes.io/region=us-east-1,topology.kubernetes.io/zone=us-east-1f
exec /entrypoint.sh: exec format error
the above error comes only when there is CPU arch mismatch btw image and the instance. In my case my Worker nodes are ARM64