fix(ci): use docker driver for buildx + drop type=gha cache (followup #173) #43
No reviewers
Labels
No Label
tier:high
tier:low
tier:medium
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: molecule-ai/molecule-core#43
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "fix/issue173-buildx-driver-and-cache"
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?
Summary
Third and final piece of #173. PR #38 + #41 fixed the Dockerfile-side clone issue (verified by CI run #893: pre-clone succeeded, COPY succeeded, image built end-to-end). #893 then surfaced two Gitea-Actions-specific issues with the unchanged buildx config:
401 Unauthorizedon ECR push — defaultdriver: docker-containerspawns a buildkit container that doesn't share the host's~/.docker/config.json. ECR auth fromamazon-ecr-loginnever reaches the push. Fix:driver: dockerso buildx uses the host daemon directly.i/o timeouton_apis/artifactcache/cache—type=ghacache is GitHub-specific; Gitea Actions has no compatible backend. Every cache lookup eats a 30s timeout. Fix: removecache-from/cache-to. Cold builds are <10min, acceptable.With this, the workflow should run end-to-end on Gitea Actions: pre-clone -> docker build (host daemon) -> ECR push.
Test plan
platform:staging-<sha>andplatform-tenant:staging-<sha>to ECR without manual operator interventionCloses #173.
Both fixes are minimal + well-scoped. driver:docker leverages host daemon ECR creds; type=gha cache removal eliminates a Gitea-incompatible code path.