From 2cd7283ce9841daabe7702449c3d5d61be683a48 Mon Sep 17 00:00:00 2001 From: Thomas Faour Date: Sat, 18 Jul 2026 15:50:11 -0400 Subject: [PATCH] Fix Gitea Actions registry auth: use a PAT instead of the auto token The automatic GITHUB_TOKEN doesn't reliably authenticate against Gitea's Container Registry -- confirmed as a known, still-open limitation across several Gitea versions (multiple upstream issues, consistent with the 401/unauthorized error hit here). Gitea's own community guidance is to use a real Personal Access Token instead. Switches docker/login-action to a REGISTRY_TOKEN repo secret (a PAT with package write scope, created in Gitea's user settings) with an explicit username rather than the gitea.actor context, and drops the now-unused permissions: packages: write block that only applied to the auto token. --- .gitea/workflows/server-docker-build.yml | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/.gitea/workflows/server-docker-build.yml b/.gitea/workflows/server-docker-build.yml index d2001ff..28fb4a2 100644 --- a/.gitea/workflows/server-docker-build.yml +++ b/.gitea/workflows/server-docker-build.yml @@ -10,9 +10,6 @@ on: jobs: build-and-push: runs-on: ubuntu-latest - permissions: - contents: read - packages: write steps: - name: Checkout uses: actions/checkout@v4 @@ -24,8 +21,8 @@ jobs: uses: docker/login-action@v3 with: registry: git.thumeit.com - username: ${{ gitea.actor }} - password: ${{ secrets.GITHUB_TOKEN }} + username: tfaour + password: ${{ secrets.REGISTRY_TOKEN }} - name: Build and push uses: docker/build-push-action@v6