[BUG] UI crashes with SIGILL on ARM64 (Raspberry Pi) in 0.8.0-beta6

[d-patch]

📋 Prerequisites

• I have searched the existing issues to avoid creating a duplicate
• By submitting this issue, you agree to follow our Code of Conduct
• I am using the latest version of the software
• I have tried to clear cache/cookies or used incognito mode (if ui-related)
• I can consistently reproduce this issue

🎯 Affected Service(s)

UI Service

🚦 Impact/Severity

Blocker

🐛 Bug Description

The nextjs process in the kagent-ui pod crashes immediately with SIGILL (Illegal Instruction) on ARM64. The UI is not usable.

🔄 Steps To Reproduce

1. Install kagent 0.8.0-beta6 on a Raspberry Pi 3 (ARM64) running
   Ubuntu 24.04.4 LTS with k3s v1.34.5+k3s1

2. helm install kagent-crds oci://ghcr.io/kagent-dev/kagent/helm/kagent-crds
   --namespace kagent --create-namespace --version 0.8.0-beta6

3. Create kagent-values.yaml:
   providers:
   default: gemini
   gemini:
   model: gemini-2.5-flash-lite
   agents:
   argo-rollouts-agent:
   enabled: false
   cilium-debug-agent:
   enabled: false
   cilium-manager-agent:
   enabled: false
   cilium-policy-agent:
   enabled: false
   helm-agent:
   enabled: false
   istio-agent:
   enabled: false
   kgateway-agent:
   enabled: false
   observability-agent:
   enabled: false
   promql-agent:
   enabled: false
   tools:
   grafana-mcp:
   enabled: false
   querydoc:
   enabled: false
   kmcp:
   enabled: false

4. helm install kagent oci://ghcr.io/kagent-dev/kagent/helm/kagent
   --namespace kagent --version 0.8.0-beta6
   -f kagent-values.yaml
   --set providers.gemini.apiKey=

5. Access the kagent UI via kubectl port-forward or Ingress

6. Open the UI in a browser

🤔 Expected Behavior

UI loads and works correctly

📱 Actual Behavior

nextjs process crashes immediately with SIGILL (core dumped) on any HTTP request. The process restarts but crashes again on each request.

💻 Environment

• kagent version: 0.8.0-beta6
• Kubernetes: k3s on Ubuntu 24.04
• Architecture: ARM64 (aarch64)
• OS: Ubuntu 24.04.4 LTS
• Kernel: 6.8.0-1048-raspi
• k3s: v1.34.5+k3s1
• Container runtime: containerd 2.1.5-k3s1

🔧 CLI Bug Report

No response

🔍 Additional Context

Version 0.7.23 works correctly on the same hardware.

📋 Logs

WARN exited: nextjs (terminated by SIGILL (core dumped); not expected)

📷 Screenshots

No response

🙋 Are you willing to contribute?

• I am willing to submit a PR to fix this issue

[EItanya]

@supreme-gg-gg Are you running on ARM? I wonder if this has to do with switching away from bun

[supreme-gg-gg]

Yea I'm running this on ARM64 Mac and I tried installing 0.8.0-beta6 and didn't run into this problem. But this could be caused by node using some native modules that are not built for the proper platform (since we moved away from bun), I'll look into it more and meanwhile feel free to share any additional information here

[d-patch]

I'm happy to share additional information to my setup. Can you please elaborate, what kind of information you would be interested in?