nginx:1.21 | redis:6.2 | gcr.io/kubernetes/kube-proxy:v1.18.3 (共 4 个镜像)

[imdingtalk]

📦 镜像列表

nginx:1.21
redis:6.2
gcr.io/kubernetes/kube-proxy:v1.18.3
lmsysorg/sglang:nightly-dev-cu13-20260824-95f5ecd3

[github-actions]

✅ 镜像同步完全成功！

查看详情

📋 同步统计

• 源镜像数: 4
• 同步任务数: 15
• ✅ 成功: 15
• ❌ 失败: 0
• 🏠 目标仓库: registry.cn-hangzhou.aliyuncs.com
• 📦 命名空间: image-speed-up

💡 说明: 每个源镜像会根据其支持的架构，同步为多个带架构后缀的目标镜像（如 nginx:1.27_amd64, nginx:1.27_arm64）

🚀 Pull 命令 (成功的镜像)

docker pull registry.cn-hangzhou.aliyuncs.com/image-speed-up/sglang:nightly-dev-cu13-20260824-95f5ecd3_amd64
docker pull registry.cn-hangzhou.aliyuncs.com/image-speed-up/sglang:nightly-dev-cu13-20260824-95f5ecd3_arm64
docker pull registry.cn-hangzhou.aliyuncs.com/image-speed-up/nginx:1.21_386
docker pull registry.cn-hangzhou.aliyuncs.com/image-speed-up/nginx:1.21_amd64
docker pull registry.cn-hangzhou.aliyuncs.com/image-speed-up/nginx:1.21_arm64
docker pull registry.cn-hangzhou.aliyuncs.com/image-speed-up/nginx:1.21_arm_v5
docker pull registry.cn-hangzhou.aliyuncs.com/image-speed-up/nginx:1.21_arm_v7
docker pull registry.cn-hangzhou.aliyuncs.com/image-speed-up/nginx:1.21_mips64le
docker pull registry.cn-hangzhou.aliyuncs.com/image-speed-up/nginx:1.21_ppc64le
docker pull registry.cn-hangzhou.aliyuncs.com/image-speed-up/nginx:1.21_s390x
docker pull registry.cn-hangzhou.aliyuncs.com/image-speed-up/redis:6.2_386
docker pull registry.cn-hangzhou.aliyuncs.com/image-speed-up/redis:6.2_amd64
docker pull registry.cn-hangzhou.aliyuncs.com/image-speed-up/redis:6.2_arm64
docker pull registry.cn-hangzhou.aliyuncs.com/image-speed-up/redis:6.2_arm_v7
docker pull registry.cn-hangzhou.aliyuncs.com/image-speed-up/redis:6.2_ppc64le

📊 详细结果

✅ lmsysorg/sglang:nightly-dev-cu13-20260824-95f5ecd3 (amd64) → registry.cn-hangzhou.aliyuncs.com/image-speed-up/sglang:nightly-dev-cu13-20260824-95f5ecd3_amd64
✅ lmsysorg/sglang:nightly-dev-cu13-20260824-95f5ecd3 (arm64) → registry.cn-hangzhou.aliyuncs.com/image-speed-up/sglang:nightly-dev-cu13-20260824-95f5ecd3_arm64
✅ nginx:1.21 (386) → registry.cn-hangzhou.aliyuncs.com/image-speed-up/nginx:1.21_386
✅ nginx:1.21 (amd64) → registry.cn-hangzhou.aliyuncs.com/image-speed-up/nginx:1.21_amd64
✅ nginx:1.21 (arm64/v8) → registry.cn-hangzhou.aliyuncs.com/image-speed-up/nginx:1.21_arm64
✅ nginx:1.21 (arm/v5) → registry.cn-hangzhou.aliyuncs.com/image-speed-up/nginx:1.21_arm_v5
✅ nginx:1.21 (arm/v7) → registry.cn-hangzhou.aliyuncs.com/image-speed-up/nginx:1.21_arm_v7
✅ nginx:1.21 (mips64le) → registry.cn-hangzhou.aliyuncs.com/image-speed-up/nginx:1.21_mips64le
✅ nginx:1.21 (ppc64le) → registry.cn-hangzhou.aliyuncs.com/image-speed-up/nginx:1.21_ppc64le
✅ nginx:1.21 (s390x) → registry.cn-hangzhou.aliyuncs.com/image-speed-up/nginx:1.21_s390x
✅ redis:6.2 (386) → registry.cn-hangzhou.aliyuncs.com/image-speed-up/redis:6.2_386
✅ redis:6.2 (amd64) → registry.cn-hangzhou.aliyuncs.com/image-speed-up/redis:6.2_amd64
✅ redis:6.2 (arm64/v8) → registry.cn-hangzhou.aliyuncs.com/image-speed-up/redis:6.2_arm64
✅ redis:6.2 (arm/v7) → registry.cn-hangzhou.aliyuncs.com/image-speed-up/redis:6.2_arm_v7
✅ redis:6.2 (ppc64le) → registry.cn-hangzhou.aliyuncs.com/image-speed-up/redis:6.2_ppc64le