34bb613c57
- 20 new high-quality edges across 8 project clusters - Edge types: BUILDS_ON, RELATED_TO, ALTERNATIVE_TO, REQUIRES - Updated relation metadata on connected memories - New episode entries and memory files from recent sessions Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.3 KiB
| id | type | title | tags | importance | confidence | created | updated | relations | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 856511bd-a987-48cf-9dfe-ee069f32beea | solution | Gitea Actions: Docker buildx registry cache auth fix |
|
0.7 | 0.8 | 2026-02-13T20:38:30.950917+00:00 | 2026-02-20T04:32:04.248740+00:00 |
|
When using Docker buildx with registry-based cache (cache-from/cache-to type=registry), the Docker Hub login step must run on ALL builds, not just main branch. Without login, PR builds fail on second run with 'push access denied, repository does not exist or may require authorization' when trying to write cache layers.
Fix: Remove the 'if: github.ref == refs/heads/main' condition from the Docker Hub login step. The push flag on build-push-action still gates actual image publishing to main-only, so this is safe.
Template location: server-configs/gitea/workflow-templates/docker-build-template.yml Affected repos: major-domo-bot, major-domo-database, paper-dynasty, paper-dynasty-database
The error manifests on the SECOND build because the first build creates cache layers successfully (fresh write), but subsequent builds fail when trying to overwrite existing layers without auth.