Build Docker CLI binaries for the LoongArch64 (loong64) architecture via CI/CD.
A GitHub Actions workflow clones the specified docker/cli version, cross-compiles with
GOOS=linux GOARCH=loong64 in a Debian 13 container, and builds docker into the
bundles/binary/ directory. Target platform: linux/loong64.
See Discussion #6 — Why Use container: debian:13? for the rationale behind the Debian 13 container choice.
Push a branch named loong64-cli-v<version> (e.g. loong64-v29.8.2) to trigger a build. Append
+<build> (e.g. loong64-v29.8.2+0) to include build metadata.
Push a tag matching release-loong64-v<version> (e.g. release-loong64-v29.8.2+0) to publish
a GitHub Release with the built binaries.
The +<build> suffix provides build metadata (e.g. +0, +1-alpha.1).
The suffix in the build metadata indicates the release stage:
| Suffix | Stage |
|---|---|
alpha |
Internal beta |
beta |
Public beta |
rc |
Pre-release |
| (none) | Stable |
Each release includes the following files:
| File | Description |
|---|---|
docker |
Docker CLI binary |
- Releases are signed with GPG.
- Download the public key from keys.openpgp.org.
- Fingerprint: FCF8724722CCBF9F51B1FBE376532BE7E3013105
- Manual download
gpg --keyserver keys.openpgp.org --recv-keys FCF8724722CCBF9F51B1FBE376532BE7E3013105
echo "FCF8724722CCBF9F51B1FBE376532BE7E3013105:6:" | gpg --import-ownertrustOr download the key file manually and import it:
gpg --import /tmp/xxxApplies to: moby-loong64, tini-loong64, cli-loong64, runc-loong64, containerd-loong64