raise `ghcr unexpected status: 403 Forbidden` when push ghcr image
See original GitHub issueTroubleshooting
Behaviour
We didn’t change any configuration before and after this error happened, same ghcr container image had permisson issue.
Steps to reproduce this issue
Expected behaviour
push successfully
Actual behaviour
#33 [auth] yikun/apache-spark-ci-image:pull,push token for ghcr.io
#33 DONE 0.0s
#32 exporting to image
#32 ...
#34 [auth] apache/spark/apache-spark-github-action-image-cache:pull yikun/apache-spark-ci-image:pull,push token for ghcr.io
#34 DONE 0.0s
#32 exporting to image
#32 pushing layers 1.5s done
#32 ERROR: unexpected status: 403 Forbidden
------
> exporting to image:
------
ERROR: failed to solve: unexpected status: 403 Forbidden
Error: buildx failed with: ERROR: failed to solve: unexpected status: 403 Forbidden
Configuration
- Repository URL (if public):
- Build URL (if public):
# paste your YAML workflow file here and remove sensitive data
Logs
https://github.com/Yikun/spark/runs/8221889583?check_suite_focus=true
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:11 (1 by maintainers)
Top Results From Across the Web
github action with docker makes error "exporting to image 403 ...
If I push code to main branch, this CI/CD pipeline works well. But my partner push code to main branch, it makes 403...
Read more >Error 403 - Forbidden when pushing to container registry
I'm getting the following error: The push refers to a repository [eu.gcr.io/my-project/das-ui] (len: 1). 26bfb51c58a5: Image push failed.
Read more >failed to solve with frontend dockerfile.v0: failed to ... - You.com
I have been trying to build image in docket but this error occured. ... to create LLB definition: unexpected status code [manifests 3.16]:...
Read more >Kubernetes ImagePullBackOff: Troubleshooting With Examples
In most cases, the error could be either from a typo or the image was not pushed to the container registry, and you're...
Read more >Resolve the Amazon ECS error when pulling Docker images ...
How do I resolve the “error pulling image configuration: error parsing HTTP 403 response body” error in Amazon ECS when pulling a Docker...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Same issue for me…
For me, relinking package to repo has fixed 403:
https://github.com/orgs/community/discussions/26274#discussioncomment-3251137