-
Notifications
You must be signed in to change notification settings - Fork 11
Open
Description
I'm currently trying to use the infisical-agent-injector in my k3s cluster, which has only arm64 nodes, but the init-container keeps crashing. After trying to debug the error I noticed that the /bin/infisical binary inside the arm64 images (and multi-arch images) seem to be build for the wrong arch:
kc run infi-debug --rm -it --command --image=infisical/cli:latest-arm64 -- /bin/sh
If you don't see a command prompt, try pressing enter.
/ # apk add file
fetch https://dl-cdn.alpinelinux.org/alpine/v3.22/main/aarch64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.22/community/aarch64/APKINDEX.tar.gz
(1/2) Installing libmagic (5.46-r2)
(2/2) Installing file (5.46-r2)
Executing busybox-1.37.0-r19.trigger
OK: 18 MiB in 19 packages
/ # file /bin/infisical
/bin/infisical: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, BuildID[sha1]=94cbdd0990f82c65eaf175f4daf449e6e97d5b95, with debug_info, not stripped
The linux_arm64 files in Releases seem to be correct, so it only seems to add a wrong file to the docker images.
Would be nice if older images could be fixed too since the infisical-agent-injector has 0.42.2 hard-coded without any way to overwrite..
Metadata
Metadata
Assignees
Labels
No labels