Exec Format Error on linux/arm64 EKS nodes - Image architecture mismatch

[Sam-tesouro]

Component(s)

controlplane, keycloak

Component version

All released versions going back at least 2 months

wgc version

N/A

controlplane version

N/A

router version

N/A

What happened?

Description

Attempting to deploy cosmo stack on EKS linux/arm64 nodes I kept hitting exec format error on images built via your build pipeline. On investigation your linux/arm64 images are reporting Architecture arm64 && Os linux on external inspection (docker inspect), but when you run uname -m from within the container they are reporting x86_64.

Steps to Reproduce

docker image inspect ghcr.io/wundergraph/cosmo/controlplane:sha-e39437b@sha256:58459b419a51e65ff0340ecb0db123440b9dea5849d1e74581b240e3d9b02dc5 | jq '.[].Architecture'

docker run --rm ghcr.io/wundergraph/cosmo/controlplane:sha-e39437b@sha256:58459b419a51e65ff0340ecb0db123440b9dea5849d1e74581b240e3d9b02dc5 uname -m

Expected Result

"arm64" "aarch64"

Actual Result

"arm64" "x86_64"

Environment information

Environment

OS: (e.g., "Ubuntu 20.04") Package Manager: pnpm, npm, yarn, etc Compiler(if manually compiled): (e.g., "go 14.2")

Router configuration

No response

Router execution config

No response

Log output

No response

Additional context

I have tested and validated this issue against Controlplane and Keycloak releases. Cosmo router is unaffected. This may effect other pipeline built images as well.

[github-actions[bot]]

WunderGraph commits fully to Open Source and we want to make sure that we can help you as fast as possible. The roadmap is driven by our customers and we have to prioritize issues that are important to them. You can influence the priority by becoming a customer. Please contact us here.

[jensneuse]

Taking a look.

[Sam-tesouro]

Hey @jensneuse, were you able to confirm the issue? Thank you!