fix(GRO-1633): add buildx network=host and provenance:false to web CI #17

Merged
Flea Flicker merged 1 commits from fix/gro-1633-web-ci-buildx into dev 2026-05-24 22:08:59 +00:00
Member

Summary

  • docker/setup-buildx-action@v3: add driver-opts: network=host — fixes DinD DNS resolution (same fix already in groombook/api)
  • docker/build-push-action@v6: add provenance: false — fixes registry push compatibility

Test plan

  • CI run on this PR completes Docker image build and push successfully
  • Image tag visible in Gitea container registry

Updated UAT_PLAYBOOK.md (N/A — CI-only change, no user-facing behaviour)

cc @cpfarhood

🤖 Generated with Claude Code

## Summary - docker/setup-buildx-action@v3: add driver-opts: network=host — fixes DinD DNS resolution (same fix already in groombook/api) - docker/build-push-action@v6: add provenance: false — fixes registry push compatibility ## Test plan - CI run on this PR completes Docker image build and push successfully - Image tag visible in Gitea container registry Updated UAT_PLAYBOOK.md (N/A — CI-only change, no user-facing behaviour) cc @cpfarhood 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Flea Flicker added 1 commit 2026-05-24 18:15:28 +00:00
fix(GRO-1633): add buildx network=host and provenance:false to web CI
CI / Test (pull_request) Successful in 20s
CI / Lint & Typecheck (pull_request) Successful in 25s
CI / Build & Push Docker Image (pull_request) Successful in 34s
f6e6c3d75f
GRO-1672 follow-up: mirror groombook/api CI fixes in groombook/web
- docker/setup-buildx-action: driver-opts network=host (DinD DNS fix)
- docker/build-push-action: provenance: false (registry push compat)

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Author
Member

The CI workflow changes (driver-opts: network=host and provenance: false) are correctly committed in this PR — the build and layer push both succeed. The remaining failure is a Gitea container registry issue: failed to push git.farh.net/groombook/web:pr-17-f6e6c3d: unknown. The registry is rejecting the image tag after layers are already pushed. This is an infrastructure issue for the CTO to investigate — not a workflow configuration issue.\n\nRe packages/repos linking: that question appears to be outside the scope of this CI fix issue. Could you clarify which packages and repos you are asking about, or raise it as a separate issue?

The CI workflow changes (driver-opts: network=host and provenance: false) are correctly committed in this PR — the build and layer push both succeed. The remaining failure is a Gitea container registry issue: `failed to push git.farh.net/groombook/web:pr-17-f6e6c3d: unknown`. The registry is rejecting the image tag after layers are already pushed. This is an infrastructure issue for the CTO to investigate — not a workflow configuration issue.\n\nRe packages/repos linking: that question appears to be outside the scope of this CI fix issue. Could you clarify which packages and repos you are asking about, or raise it as a separate issue?
Flea Flicker merged commit db892409ef into dev 2026-05-24 22:08:59 +00:00
Sign in to join this conversation.