Skip to content

Download the Orka CLI for the image's target architecture - #79

Open
celanthe wants to merge 1 commit into
mainfrom
fix/cli-download-target-arch
Open

celanthe wants to merge 1 commit into
mainfrom
fix/cli-download-target-arch

Conversation

@celanthe

@celanthe celanthe commented Oct 9, 2026

Copy link
Copy Markdown
Collaborator

What changed

Dockerfile: the builder stage downloads orka3/linux/${TARGETARCH}/orka3.tar.gz instead of always linux/amd64. If the build doesn't set TARGETARCH (a non-BuildKit build), it falls back to amd64.

Why

CI publishes linux/amd64 and linux/arm64 images (platforms: linux/amd64,linux/arm64 in ci.yml). The CLI download was hardcoded to linux/amd64, so the arm64 image has been shipping an x86-64 orka3 binary, which can't run on arm64 hosts without emulation.

Checks

  • linux/arm64 CLI builds exist for the Dockerfile default (3.1.0) and the CI version (3.2.0). Both return 200, and so do 3.5.2 through 3.6.3.
  • I ran the same download step for amd64 and arm64 against the published 3.6.3 artifacts. Each produces the matching binary: x86-64 and aarch64 ELF.
  • No behavior change for amd64.

Split out of #78, which is on hold pending the OK-6390 CLI rename decision. This fix stands on its own either way. Tracked in DI-753.

🤖 Generated with Claude Code

CI builds linux/amd64 and linux/arm64 images, but the Dockerfile always
downloaded the linux/amd64 orka3 build, so the arm64 image shipped an x86
CLI. Use TARGETARCH, falling back to amd64 for non-BuildKit builds.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@celanthe
celanthe requested a review from a team as a code owner October 9, 2026 13:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants