Deployment to raspberry PI (Arm64) fails

[mrsimpson]

Motivation

I want to to try out Kong as API-gateway on my PI 4 running K8S.

Expectation

I figured that the image used in the current chart version does not find an image for the arm64 architecture, but found out there was a dedicated docker image for arm, so I overrode that.

What happens

Still, I was unsuccessful spinning up a pod of arm64v8/kong:ubuntu.
Output on stdout:

standard_init_linux.go:211: exec user process caused "exec format error"

This indicates the platform does not match.

I am not 100% sure this is the place to ask, since my setup is K8S (K3S distribution) and deployment via Helm, so feel free to redirect!

Observations

I installed with

helm install kong --namespace=kong --skip-crds --set ingressController.installCRDs=false --set image.repository=arm64v8/kong --set image.tag=ubuntu kong/kong

The pod triggered seems to hold the proper (overridden) image (from kubectl describe):

proxy:
    Container ID:   containerd://211e508357f16194b8a6c003579c26ace13c87408a91396b479a5f52f91d3a19
    Image:          arm64v8/kong:ubuntu
    Image ID:       docker.io/arm64v8/kong@sha256:39e4b224efc8b79152c7f2cdc7fd9f89e86dbb514b8257cf2e246bcc41f78a8a

Thanks for your support and the great work on Kong!
Oliver

Remark: this is a crossposting from the docker-kong repo, since I really don't understand to which part (chart, image) the issue is more related to. Linking those issues.

[hbagdi]

@hutchic How do use arm64 Docker image of Kong? Does the Docker repo or tag change?

[hutchic]

I can't reproduce using a arm64 ec2 instance

docker run -it --rm arm64v8/kong:ubuntu kong version
Unable to find image 'arm64v8/kong:ubuntu' locally
ubuntu: Pulling from arm64v8/kong
185661474c6b: Pull complete
053aaa7a7ba3: Pull complete
80ccb1337bb9: Pull complete
f6d1fb143b02: Pull complete
b909805820cf: Pull complete
71704f38eaf4: Pull complete
Digest: sha256:39e4b224efc8b79152c7f2cdc7fd9f89e86dbb514b8257cf2e246bcc41f78a8a
Status: Downloaded newer image for arm64v8/kong:ubuntu

2.0.1

ubuntu@docker-machine-arm64-ubuntu:~$ uname -a
Linux docker-machine-arm64-ubuntu 4.15.0-1043-aws #45-Ubuntu SMP Mon Jun 24 14:08:49 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux

ubuntu@docker-machine-arm64-ubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.2 LTS
Release:        18.04
Codename:       bionic

Can you send the output of lsb_release -a and uname -a?

[mrsimpson]

sure!

lsb_release -a
No LSB modules are available.
Distributor ID:	Raspbian
Description:	Raspbian GNU/Linux 10 (buster)
Release:	10
Codename:	buster

uname -a
Linux raspberrypi 4.19.97-v7l+ #1294 SMP Thu Jan 30 13:21:14 GMT 2020 armv7l GNU/Linux

May there be the culprit? armv7l? I assumed the PI 4 has got an armv8 processor

Remark: I try running it inside a K3S-Kubernetes cluster. So there's no docker, but only containerd. This shouldn't make a difference as per my understanding though.

[hutchic]

armv7l (in Docker terminology arm32v7) is indeed the culprit as it's a 32 bit processor and running a
arm64v8 image won't work.

If there's enough demand we can look into building arm32v7

[charlie-haley]

I'd also be interested in a arm32v7 build at some point in the future!

[Sonlis]

I would be interested too!