Skip to content
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

Echo images for Consul API Gateway are not arm64-compatible #65

Closed
nathancoleman opened this issue Jun 7, 2022 · 0 comments · Fixed by #67
Closed

Echo images for Consul API Gateway are not arm64-compatible #65

nathancoleman opened this issue Jun 7, 2022 · 0 comments · Fixed by #67
Labels
bug Something isn't working consul

Comments

@nathancoleman
Copy link
Member

nathancoleman commented Jun 7, 2022

The image used for echo-1 and echo-2 in the local Consul API Gateway setup are not compatible with arm64 machines (M1 Macs, for example).

The echo services go into a crash loop with the error:

Generating self-signed cert
Generating a 2048 bit RSA private key
...............................+++
.......................................................................................................+++
writing new private key to '/certs/privateKey.key'
-----
Starting nginx
PANIC: unprotected error in call to Lua API (bad light userdata pointer)

According to kubernetes/ingress-nginx#2802, this is because Lua didn't previously support arm64 architectures. The image we're currently using has fallen out of date.

I was able to get the setup working with a similar image - k8s.gcr.io/ingressconformance/echoserver:v0.0.1 - and some port adjustments; however, the repo has changed significantly since then. I'm hoping to be able to update my branch and make a PR soon. In the meantime, I figured I would document the issue here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working consul
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant