Prebuilt Docker images for go-containerregistry CLI tools — crane, gcrane, and krane — on LoongArch64 (loong64).
Official upstream already provides loong64 binaries from v0.21.8 onwards. This project packages those binaries into ready-to-use Docker images.
Images are built on Anolis OS and support the following CPU architectures:
| Architecture |
|---|
amd64 |
arm64 |
loong64 |
Prebuilt images are published to the following registries:
Docker Hub:
kubernetesloong64/cranekubernetesloong64/gcranekubernetesloong64/krane
Alibaba Cloud (Qingdao):
registry.cn-qingdao.aliyuncs.com/kubernetesloong64/craneregistry.cn-qingdao.aliyuncs.com/kubernetesloong64/gcraneregistry.cn-qingdao.aliyuncs.com/kubernetesloong64/krane
# Docker Hub
kubernetesloong64/crane:v0.22.0-anolis
kubernetesloong64/gcrane:v0.22.0-anolis
kubernetesloong64/krane:v0.22.0-anolis
# Alibaba Cloud (Qingdao)
registry.cn-qingdao.aliyuncs.com/kubernetesloong64/crane:v0.22.0-anolis
registry.cn-qingdao.aliyuncs.com/kubernetesloong64/gcrane:v0.22.0-anolis
registry.cn-qingdao.aliyuncs.com/kubernetesloong64/krane:v0.22.0-anolis
docker run --rm registry.cn-qingdao.aliyuncs.com/kubernetesloong64/crane:v0.22.0-anolis crane version
docker run --rm registry.cn-qingdao.aliyuncs.com/kubernetesloong64/gcrane:v0.22.0-anolis gcrane version
docker run --rm registry.cn-qingdao.aliyuncs.com/kubernetesloong64/krane:v0.22.0-anolis krane versionPush a branch named loong64-v<version> (e.g. loong64-v0.22.0) to trigger a build. Append
+<build> (e.g. loong64-v0.22.0+0) to include build metadata.
Push a tag matching release-loong64-v<version> (e.g. release-loong64-v0.22.0+1) to publish
a GitHub Release with the built Docker images.
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 |
|---|---|
*.tar |
Docker image archive |
Each file has a corresponding .asc detached GPG signature.
- 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/xxxEach release artifact has a corresponding .asc detached signature. To verify, download both the file and its .asc
signature from the release, then:
gpg --verify <file>.asc <file>