docker / docker/build-push-action
Misleading error instead of denied: registry contains 1 repositories, limit is 1
Open
Nobody has claimed this yet.
kind/upstream
- Dominant language
- TypeScript
- Stars
- 5.4k
- Forks
- 735
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 14
Description
Is this an upstream issue?
error: failed to solve: failed to fetch oauth token: unexpected status: 403 Forbidden
vs what you get in docker push manually
denied: registry contains 1 repositories, limit is 1
Originally posted by @adriangabura in https://github.com/docker/build-push-action/issues/585#issuecomment-1087944326
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by reproducing the registry limit during a Docker image build-and-push through this GitHub Action, then compare its 403 output with a manual docker push. Done means the action reports the registry's denied message instead of the misleading OAuth-token error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100