-
Notifications
You must be signed in to change notification settings - Fork 655
Exec format error on arm64 #797
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I can confirm this: % docker run -it --rm --entrypoint sh --platform linux/arm64 registry.k8s.io/node-problem-detector/node-problem-detector:v0.8.14
# apt update && apt -y install file
Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB]
Get:2 http://deb.debian.org/debian-security bullseye-security InRelease [48.4 kB]
Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Get:4 http://deb.debian.org/debian bullseye/main arm64 Packages [8071 kB]
Get:5 http://deb.debian.org/debian-security bullseye-security/main arm64 Packages [241 kB]
Get:6 http://deb.debian.org/debian bullseye-updates/main arm64 Packages [14.9 kB]
...
# file node-problem-detector
node-problem-detector: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bd9bd59069612b94e84e1c60d73ebf61d618cd44, for GNU/Linux 3.2.0, with debug_info, not stripped
# file bin/ls
bin/ls: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, BuildID[sha1]=9c1a4999161b8b2da681b80d8bf351e40afc40ad, for GNU/Linux 3.7.0, stripped /kind bug |
Same experience here |
have you solve this problem? |
Hi, it's been a while. Has anyone been able to work around this error? |
When using the image
registry.k8s.io/node-problem-detector/node-problem-detector:v0.8.14
on arm64 nodes the pod crash loops with the following error:exec /node-problem-detector: exec format error
Pod manifest:
The text was updated successfully, but these errors were encountered: