-
Notifications
You must be signed in to change notification settings - Fork 673
Version 2.7.0 doesn't work on armv7 #3842
Comments
Your first example is running The |
? Latest currently matches 2.7.0
Which caused this as well when running Current workaround is to use the 2.6.5 image. |
Can you run |
I'm seeing this as well. when moving from 2.6.2 -> 2.7.0
(k8node2 is aarch64, k8master & k8node1 are armv7)
I pulled it regardless (probably the same image with multiple tags?)
|
yeah using kubeadm I was showing |
Hi I could pinpoint it down to On ARM systems I just see the illegal instruction, but with x86 qemu-arm and strace I could locate it here: while weaver from 2.6.5 does this here: As 2.6.5 is working, the question it had changed at this part of the code (or on how the code was compiled). docker inspect weaveworks/weave-kube:2.7.0 |
Same error as @FoxRomeo with RPi4 5.4.51-v7l+ (k8s: v1.18.8), works with weave 2.6.5 |
New RPI4 cluster and after installing Weave, all my Weave pods were CrashedLoopbackOff with error code 132. Installed 2.6.5 instead of 2.7.0 and everything is working. |
As a side note, I switched my PRI4 cluster to Ubuntu 20 server arm64 and found compatibility to be much better across the board. Strongly recommend. |
same issue on Rpi3, same workaround (use 2.6.5) |
I fired up a 'C1' machine on Scaleway and tried to run 2.7.0; it is an ARM 32-bit binary but crashed immediately with segmentation fault on startup. I don't get an illegal instruction. I rebuilt the Weave Net daemon ( |
If I take away the linker flags for static linking it doesn't crash. After about a day of bisecting I came to the conclusion that it is the newer version of the Kubernetes client-go library which is triggering the crash, somehow in conjunction with CGo and static linking on ARM32. The good news is this code can easily be moved to the If someone tries that out please comment here how it went. |
That change is now released in Weave Net 2.8.1 and I have tested |
What you expected to happen?
Weave image should start on Raspberry Pi 4.
What happened?
exec user process caused "exec format error"
Illegal instruction (core dumped)
How to reproduce it?
Anything else we need to know?
Versions:
The text was updated successfully, but these errors were encountered: