cal/major-domo-v2
1
0
Fork 0
Code Issues 6 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

ci: switch Docker build cache from type=gha to type=registry
Some checks failed
Build Docker Image / build (pull_request) Failing after 16s
Details

Browse Source 
The gha cache backend silently fails on Gitea Actions due to Docker
networking issues between the Buildx builder container and the
act_runner cache server. Registry-based caching stores layers on
Docker Hub, which is more reliable for self-hosted runners.
This commit is contained in:
cal 2026-02-11 22:12:21 +00:00
parent 0ed0446607
commit d72595cef7
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
.gitea/workflows/docker-build.yml
View File

@ -194,8 +194,8 @@ jobs:
manticorum67/major-domo-discordapp:latest
manticorum67/major-domo-discordapp:v${{ steps.meta.outputs.version }}
manticorum67/major-domo-discordapp:${{ steps.meta.outputs.version_sha }}
cache-from: type=gha
cache-to: type=gha,mode=max
cache-from: type=registry,ref=manticorum67/major-domo-discordapp:buildcache
cache-to: type=registry,ref=manticorum67/major-domo-discordapp:buildcache,mode=max
# ==============================================
# 7. BUILD SUMMARY
@ -368,8 +368,8 @@ jobs:
# - Check webhook still exists in Discord channel settings
#
# 4. Build cache not working
# - GitHub Actions cache is stored per repository
# - Cache is shared across branches
# - May need to clear cache if corrupted
# - Uses registry-based caching (pushes cache layers to Docker Hub)
# - Requires Docker Hub login to read/write cache
# - To clear cache: delete the buildcache tag on Docker Hub
#
# ==============================================