fix(ci): isolate publish buildx docker config #1641
Reference in New Issue
Block a user
Delete Branch "fix/publish-buildx-docker-config"
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
Why
The fresh staging peer-visibility E2E exposed that the tenant image is stale: the admin workspace-token route exists in main, but the post-merge publish job failed before building with EACCES creating /home/hongming/.docker-ecr/buildx/certs. Without a successful publish, fresh tenants continue booting an older platform-tenant:staging-latest image and POST /admin/workspaces/:id/tokens falls through to Canvas.
Tests
Approving CI-only publish fix. Required CI aggregate is green; change is scoped to writable DOCKER_CONFIG before setup-buildx.
Approving CI-only publish fix.
devops approval: CI-only publish runner fix; required CI aggregate green; change scopes DOCKER_CONFIG to RUNNER_TEMP before setup-buildx.
infra approval: fixes publish runner Buildx config ownership; required CI aggregate green.