Prisma Cloud Compute: How to resolve "exec /usr/local/bin/defender: exec format error" while installing defenders
3413
Created On 10/27/23 01:32 AM - Last Modified 11/22/24 14:33 PM
Objective
The objective of this article is to successfully install defenders on a supported environment and avoid getting the following error:
Warning BackOff 2m38s (x24 over 7m46s) kubelet Back-off restarting failed container twistlock-defender in pod twistlock-defender-ds-4b2bh_twistlock(ca14f9c1-6ab8-44ac-946e-3b233c90ab7a) exec /usr/local/bin/defender: exec format error
Environment
- Prisma Cloud Compute SaaS version
- Prisma Cloud Compute Self-Hosted version
Procedure
The defender image in our twistlock registry does not have a tag to differentiate between x86_64 and arm64 images. It pulls the correct image using the architecture of the host that it is being pulled on. Hence, the error occurs when users pull twistlock defender image and upload it to their private registry using arm64 architecture. Then they use the image from private registry to deploy in a x86_64 environment.
To resolve this issue, users should use x86_64 machine to pull the image from twistlock registry if they are deploying on a x86_64 environment.
Additional Information
The opposite is also true. If users want to deploy in arm64 environment then they would need to use arm64 machine to pull the defender image from twistlock registry and upload it to their private registry. Then use the same image to deploy in their environment.