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

[imdingtalk]

📦 镜像列表

nginx:1.21
redis:6.2
gcr.io/kubernetes/kube-proxy:v1.18.3
ghcr.io/0xsero/deepseek-v4-flash-0731-spark-sparkinfer@sha256:2e077489a83a0360952828051fe7f7a32c1801e5ce8436d85f7267583d614ff4
lmsysorg/sglang:qwen38-27b

[github-actions]

✅ 镜像同步完全成功！

查看详情

📋 同步统计

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

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

⏭️ 跳过的镜像

以下镜像无法获取信息，已跳过：

- gcr.io/kubernetes/kube-proxy:v1.18.3
  原因: time="2026-08-25T08:29:39Z" level=fatal msg="Error parsing image name \"docker://gcr.io/kubernetes/kube-proxy:v1.18.3\": Requesting bear token: invalid status code from registry 403 (Forbidden)"

常见原因：

• 镜像不存在或已被删除
• 源仓库访问受限（需要认证或地区限制）
• 镜像名称或标签错误
• 网络问题或源仓库不可用

建议：

• 检查镜像名称和标签是否正确
• 尝试访问源仓库确认镜像是否存在
• 使用 skopeo inspect docker://<镜像名> 手动测试

🚀 Pull 命令 (成功的镜像)

docker pull registry.cn-hangzhou.aliyuncs.com/image-speed-up/deepseek-v4-flash-0731-spark-sparkinfer:2e077489a83a_arm64
docker pull registry.cn-hangzhou.aliyuncs.com/image-speed-up/sglang:qwen38-27b_amd64
docker pull registry.cn-hangzhou.aliyuncs.com/image-speed-up/sglang:qwen38-27b_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

📊 详细结果

✅ ghcr.io/0xsero/deepseek-v4-flash-0731-spark-sparkinfer@sha256:2e077489a83a0360952828051fe7f7a32c1801e5ce8436d85f7267583d614ff4 (arm64) → registry.cn-hangzhou.aliyuncs.com/image-speed-up/deepseek-v4-flash-0731-spark-sparkinfer:2e077489a83a_arm64
✅ lmsysorg/sglang:qwen38-27b (amd64) → registry.cn-hangzhou.aliyuncs.com/image-speed-up/sglang:qwen38-27b_amd64
✅ lmsysorg/sglang:qwen38-27b (arm64) → registry.cn-hangzhou.aliyuncs.com/image-speed-up/sglang:qwen38-27b_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