Code-Inc/WatchLink
2
1
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Configure REGISTRY_TOKEN with package write permission #1

New Issue
Closed
opened 2026-05-15 02:45:11 +00:00 by MrSphay · 0 comments
MrSphay commented 2026-05-15 02:45:11 +00:00
Owner
Copy Link

The WatchLink Docker build now reaches the publish step, but pushing git.wilkensxl.de/mrsphay/watchlink:latest fails with 401 Unauthorized during blob upload.

Observed in Gitea Actions build run:

  • Docker build completes.
  • docker push starts uploading layers.
  • Registry returns 401 Unauthorized for POST https://git.wilkensxl.de/v2/mrsphay/watchlink/blobs/uploads/.

Impact:

  • The repository builds successfully, but the Docker image cannot be published to the Gitea container registry.

Suggested fix:

  • Create or update repository/org secret REGISTRY_TOKEN with package/container write permission for owner MrSphay.
  • Re-run the Build workflow after updating the secret.
  • Verify that package watchlink:latest appears under Gitea container packages.

Verification already performed:

  • Repository is public.
  • Latest Dockerfile fixes allow the Docker image build to proceed.
  • Failure is isolated to registry upload authorization.
The WatchLink Docker build now reaches the publish step, but pushing `git.wilkensxl.de/mrsphay/watchlink:latest` fails with `401 Unauthorized` during blob upload. Observed in Gitea Actions build run: - Docker build completes. - `docker push` starts uploading layers. - Registry returns `401 Unauthorized` for `POST https://git.wilkensxl.de/v2/mrsphay/watchlink/blobs/uploads/`. Impact: - The repository builds successfully, but the Docker image cannot be published to the Gitea container registry. Suggested fix: - Create or update repository/org secret `REGISTRY_TOKEN` with package/container write permission for owner `MrSphay`. - Re-run the Build workflow after updating the secret. - Verify that package `watchlink:latest` appears under Gitea container packages. Verification already performed: - Repository is public. - Latest Dockerfile fixes allow the Docker image build to proceed. - Failure is isolated to registry upload authorization.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
MrSphay Toxic
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Code-Inc/WatchLink#1
Delete Branch "%!s()"

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?