rtk-ai/rtk

Add aarch64-unknown-linux-musl target to release binaries

Open

#1,331 建立於 2026年4月15日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)Rust (48,085 star) (2,914 fork)batch import
effort-smallenhancementgood first issue

描述

Problem

The current release only provides rtk-aarch64-unknown-linux-gnu.tar.gz for Linux ARM64. This binary is not compatible with Alpine Linux (musl libc), which is widely used in container images.

Running the gnu binary on Alpine results in:

Error relocating /usr/local/bin/rtk: fcntl64: symbol not found
Error relocating /usr/local/bin/rtk: __res_init: symbol not found

Even with libc6-compat and gcompat packages installed, the missing symbols are not resolved.

Current workaround

We build rtk from source using Cargo inside an Alpine-based Docker stage, which works but adds significant build time (~3-5 min)
compared to downloading a pre-built binary.

Request

Add rtk-aarch64-unknown-linux-musl.tar.gz to the release assets, similar to how rtk-x86_64-unknown-linux-musl.tar.gz is already provided for x86_64.

Context

  • The x86_64 musl target already exists: rtk-x86_64-unknown-linux-musl.tar.gz
  • Alpine Linux is the de facto standard for lightweight container images
  • ARM64 (aarch64) adoption is growing fast in cloud (AWS Graviton, Azure Cobalt, etc.)
  • The Rust target aarch64-unknown-linux-musl is Tier 2 with host tools, so cross-compilation should be straightforward

Thanks for the great tool! 🚀

貢獻者指南

技術棧
rust
領域
devopsrelease
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Rust cross compilation basicsGitHub Actions workflow understanding
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70
研究方向
Locate the release workflow file in `.github/workflows/` (likely `release.yml`). Identify where the x86 64 musl target is defined (e.g., `x86 64 unknown linux musl`). Add a similar entry for `aarch64 unknown linux musl`, ensuring the cross compilation toolchain (e.g., `rustup target add aarch64 unknown linux musl`) is installed in the workflow. Optionally, test the build locally using `cargo build target aarch64 unknown linux musl` with an appropriate linker. Create a pull request with the change and reference this issue.