FrederikBaerentsen/BrickTracker
8
20
Fork 12
Code Issues 10 Pull Requests Actions Packages Projects 1 Releases 9 Wiki Activity

Error when I try to pull the latest image #155

New Issue
Closed
opened 2026-04-23 14:29:39 +02:00 by derwohat · 4 comments
derwohat commented 2026-04-23 14:29:39 +02:00
Copy Link
Copy Source

Hi Frederik,

I got the message from Dockhand that there is a new version available, but when I try to update I get this error:

Pull failed: Failed to pull image: {"message":"Head "https://gitea.baerentsen.space/v2/frederikbaerentsen/bricktracker/manifests/latest": no basic auth credentials"}

Is it only me?

Hi Frederik, I got the message from Dockhand that there is a new version available, but when I try to update I get this error: Pull failed: Failed to pull image: {"message":"Head \"https://gitea.baerentsen.space/v2/frederikbaerentsen/bricktracker/manifests/latest\": no basic auth credentials"} Is it only me?
FrederikBaerentsen commented 2026-04-23 15:34:16 +02:00
Owner
Copy Link
Copy Source

Hmm, that's weird. What happens if you pull the images normally like docker compose pull ?

Hmm, that's weird. What happens if you pull the images normally like `docker compose pull` ?
FrederikBaerentsen added the Kind/Bug label 2026-04-23 15:34:20 +02:00
Ventje23 commented 2026-04-23 19:19:08 +02:00
Copy Link
Copy Source

I had the same message using portainer, had to log in to gitea (section registries) and message disapeared

I had the same message using portainer, had to log in to gitea (section registries) and message disapeared
FrederikBaerentsen commented 2026-04-23 22:00:32 +02:00
Owner
Copy Link
Copy Source

It is a bug in the latest Gitea version (see https://github.com/go-gitea/gitea/issues/37326). I updated to the latest nightly version and it should work again.

Let me know if you still have issues!

It is a bug in the latest Gitea version (see https://github.com/go-gitea/gitea/issues/37326). I updated to the latest nightly version and it should work again. Let me know if you still have issues!
derwohat commented 2026-04-24 14:08:21 +02:00
Author
Copy Link
Copy Source

Yes, it works again. Thanks for helping!

Yes, it works again. Thanks for helping!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
 Out of Scope
Request is out of scope
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Unraid
Unsupported/Can't help
No Label Kind/Bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
FrederikBaerentsen
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#155
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?