xiaoxia/xiaoxia-saas
1
0
Fork 0
Code Issues 10 Pull Requests 2 Actions Packages Projects Releases 7 Wiki Activity

fix(ci): 配置docker-container buildx builder修复cache export失败 #320

Merged
xiaoxia merged 1 commits from fix/ci-buildx-builder into develop 2026-07-14 15:37:58 +08:00
Conversation 1 Commits 1 Files Changed 1
+99 -15
xiaoxia commented 2026-07-14 15:29:59 +08:00
Owner
Copy Link
Copy Source

问题

新CI服务器上Docker使用默认docker driver，不支持buildx的--cache-to导出功能，导致所有Staging/Production镜像构建直接失败：

ERROR: Cache export is not supported for the docker driver.

develop分支当前CI全红（3个Staging构建全挂）。

修复方案

在6个镜像构建Job（3个Staging + 3个Production）的Build步骤前，统一添加Setup buildx builder步骤：

  • 检查是否已有ci-builder实例，没有则用docker buildx create --use --driver docker-container创建
  • 已存在则直接docker buildx use ci-builder切换
  • docker buildx inspect --bootstrap确保builder启动就绪

变更范围

  • .gitea/workflows/ci-cd.yml: 6个构建Job各加1个builder初始化步骤
  • 不影响门禁Job（Validate/Unit/Frontend Lint等）
## 问题 新CI服务器上Docker使用默认`docker` driver，不支持buildx的`--cache-to`导出功能，导致所有Staging/Production镜像构建直接失败： ``` ERROR: Cache export is not supported for the docker driver. ``` develop分支当前CI全红（3个Staging构建全挂）。 ## 修复方案 在6个镜像构建Job（3个Staging + 3个Production）的Build步骤前，统一添加`Setup buildx builder`步骤： - 检查是否已有`ci-builder`实例，没有则用`docker buildx create --use --driver docker-container`创建 - 已存在则直接`docker buildx use ci-builder`切换 - `docker buildx inspect --bootstrap`确保builder启动就绪 ## 变更范围 - `.gitea/workflows/ci-cd.yml`: 6个构建Job各加1个builder初始化步骤 - 不影响门禁Job（Validate/Unit/Frontend Lint等）
xiaoxia added 1 commit 2026-07-14 15:29:59 +08:00
fix(ci): 配置docker-container buildx builder以支持cache export
CI/CD Pipeline / Validate Code Quality And Tests (pull_request) Successful in 31s
Details
CI/CD Pipeline / Unit Tests (pull_request) Successful in 1m26s
Details
CI/CD Pipeline / Integration Tests (pull_request) Successful in 1m13s
Details
CI/CD Pipeline / Frontend Lint (pull_request) Successful in 2m11s
Details
CI/CD Pipeline / Build Staging API Image (pull_request) Has been skipped
Details
CI/CD Pipeline / Build Staging Worker Image (pull_request) Has been skipped
Details
CI/CD Pipeline / Build Staging Web Image (pull_request) Has been skipped
Details
CI/CD Pipeline / Build Production API Image (pull_request) Has been skipped
Details
CI/CD Pipeline / Build Production Worker Image (pull_request) Has been skipped
Details
CI/CD Pipeline / Build Production Web Image (pull_request) Has been skipped
Details
CI/CD Pipeline / Deploy Staging (Watchtower auto-deploy) (pull_request) Has been skipped
Details
CI/CD Pipeline / Staging E2E Tests (pull_request) Has been skipped
Details
CI/CD Pipeline / Staging API Integration Tests (pull_request) Has been skipped
Details
CI/CD Pipeline / Deploy Production (pull_request) Has been skipped
Details
CI/CD Pipeline / Production Browser E2E (pull_request) Has been skipped
Details
3d1b739e7f 
新CI服务器默认docker driver不支持buildx cache export功能，
导致Staging/Production构建直接失败：
ERROR: Cache export is not supported for the docker driver.

在6个镜像构建Job中统一添加builder初始化步骤，
自动创建/使用docker-container类型的builder实例。
xiaoxia reviewed 2026-07-14 15:37:49 +08:00
xiaoxia left a comment
Author
Owner
Copy Link
Copy Source

LGTM - 4个核心门禁全绿，builder修复方案正确

LGTM - 4个核心门禁全绿，builder修复方案正确
xiaoxia merged commit f867897348 into develop 2026-07-14 15:37:58 +08:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
P0
阻塞性，必须立即处理
 P1
高优先级
 P2
中优先级
 P3
低优先级/后考虑
 architecture
架构设计
 backend
后端相关
 blocked
阻塞中
 bug
Bug修复
 ci-bug
CI本身的bug
 ci-optimization
CI优化类任务
 ci-pipeline
CI流水线/workflow相关
 cleanup
代码清理
 devops
运维/部署/CI
 documentation
文档相关
 feature
新功能
 frontend
前端相关
 question
需要讨论确认
 ready
PR CI通过，可合并
 refactor
代码重构
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
auto-approve-bot xiaoxia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: xiaoxia/xiaoxia-saas#320
Delete Branch "fix/ci-buildx-builder"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?