metallb: 0.13.2: multi-arch images broken

It looks like multi-arch images are broken in 0.13.2:

ubuntu@pi01:~$ uname -a
Linux pi01 5.4.0-1065-raspi #75-Ubuntu SMP PREEMPT Fri Jun 3 14:24:57 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux

ubuntu@pi01:~$ docker run -it --rm quay.io/metallb/controller:v0.12.1
{"branch":"HEAD","caller":"level.go:63","commit":"v0.12.1","goversion":"gc / go1.16.14 / arm64","level":"info","msg":"MetalLB controller starting version 0.12.1 (commit v0.12.1, branch HEAD)","ts":"2022-07-06T16:43:05.750879466Z","version":"0.12.1"}
{"caller":"level.go:63","error":"open /var/run/secrets/kubernetes.io/serviceaccount/namespace: no such file or directory","level":"error","msg":"Unable to get namespace from pod service account data, please specify --namespace or METALLB_NAMESPACE","op":"startup","ts":"2022-07-06T16:43:05.751340719Z"}

ubuntu@pi01:~$ docker run -it --rm quay.io/metallb/controller:v0.13.2
standard_init_linux.go:228: exec user process caused: exec format error

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 2
  • Comments: 22 (12 by maintainers)

Most upvoted comments

Thanks @werwolfb! We need to wait a couple of prs to get in and we’ll do a new release.

  • k3s HA with 3 nodes on v1.23.8+k3s2
  • metallb v0.13.3
  • helm chart
  • metallb configuration
  • deploy cmd: helm install --create-namespace --namespace metallb metallb metallb/metallb -f metallb-values.yml

Will try full installation on clean PIs cluster in the morning (in ~8 hours).

Will let you know, thank you!

0.13.3 is out

@fedepaol I’ve checked on my pi:

docker run -it --rm quay.io/fpaoline/controller:v1.100.3
Unable to find image 'quay.io/fpaoline/controller:v1.100.3' locally
v1.100.3: Pulling from fpaoline/controller
b3c136eddcbf: Already exists
04375d82adcb: Pull complete
9b3225ea2360: Pull complete
Digest: sha256:52c80bb0cf1a71b85b1ce4e5de270331dc771a147379ff6305d089da970cb428
Status: Downloaded newer image for quay.io/fpaoline/controller:v1.100.3
{"branch":"dev","caller":"main.go:141","commit":"dev","goversion":"gc / go1.18.3 / arm64","level":"info","msg":"MetalLB controller starting (commit dev, branch dev)","ts":"2022-07-07T07:29:13Z","version":""}
{"caller":"main.go:146","error":"open /var/run/secrets/kubernetes.io/serviceaccount/namespace: no such file or directory","level":"error","msg":"Unable to get namespace from pod service account data, please specify --namespace or METALLB_NAMESPACE","op":"startup","ts":"2022-07-07T07:29:13Z"}

Looks like this tag exactly works. Thank you.

We’ll publish a 0.13.3, probably tomorrow my morning (in 8 hours), because we don’t want to recreate images with the same tag but different shas.