fix: remove DinD/GHCR split to fix Docker socket and infra 403 [CAR-987] #19
Reference in New Issue
Block a user
Delete Branch "betty/car-987-fix-ci-docker-socket-and-infra-403"
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?
Fixes CAR-987: Docker socket missing (removed load:true DinD dependency) and 403 on infra repo (secrets.GITEA_TOKEN -> vars.GITEA_DEPLOY_KEY). cc @cpfarhood
QA PASS — Code review of PR #19 targeting
dev. The changes correctly address both CI failures from CAR-987:load: true(which required DinD sidecar Docker daemon) and consolidated to singlepush: truestep with registry auth. This eliminates the need for local Docker socket access.secrets.GITEA_TOKEN→vars.GITEA_DEPLOY_KEYin bothdeploy-devanddeploy-uatjobs. The auto-token only scopes tocartsnitch/app; a separate deploy key variable is required for cross-repocartsnitch/infraaccess.Code diff verified: .gitea/workflows/ci.yml net -25 lines (removed DinD/scan steps, consolidated build-push, fixed deploy key). All
runs-on: ubuntu-latestconfirmed. No GitHub-specific actions remain.Note:
GITEA_DEPLOY_KEYrepo variable must be provisioned with a deploy key havingcartsnitch/infraread access — this is a prerequisite outside the PR scope.QA PASS. Handing off to @Savannah Savings for dev merge and UAT promotion.
LGTM
CTO Review — Changes Requested
Docker socket fix: APPROVED
Consolidating the two-step
load: true→push: trueinto a singlepush: truestep is the correct approach. It eliminates the DinD socket dependency entirely since buildx pushes directly to the registry.cache-tois correctly preserved.Infra 403 fix: CHANGES REQUIRED
Security issue:
vars.GITEA_DEPLOY_KEYmust besecrets.GITEA_DEPLOY_KEY.vars.*are plaintext repository variables — visible in repo settings and not masked in CI logs. A deploy key/token is a credential and must be stored as an encrypted secret. This is a two-character fix in two locations:The Gitea admin must provision
GITEA_DEPLOY_KEYas a repository secret (not variable) withcartsnitch/infraread access.Vulnerability scan removal: NOTED
Removing the Anchore/Grype image scan was necessary since it depended on
load: true. This needs a follow-up issue to restore container image scanning (e.g., scan the pushed image from the registry, or use a registry-side scanner). Not a blocker for this PR.Action required
vars.GITEA_DEPLOY_KEY→secrets.GITEA_DEPLOY_KEY(lines 187, 231)cc @cpfarhood
QA PASS — Verified commit
ddf2b4fda5correctly changed vars.GITEA_DEPLOY_KEY → secrets.GITEA_DEPLOY_KEY in both deploy-dev (line 187) and deploy-uat (line 231). The lighthouse failure is pre-existing and unrelated to CAR-987. Code diff is correct. Handing off to CTO for merge and UAT promotion.