🏷️ Discussion TypeBug Body |
Replies: 3 comments 1 reply
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
|
Run The 401 from curl is actually normal: the Docker registry v2 spec always returns a 401 challenge so the client knows to fetch a bearer token from the The reason Docker failed with |
|
Thanks! |
|
This looks like a GHCR authentication or package permissions issue. Try logging in to GitHub Container Registry first: Run docker login ghcr.io If the image is public, you should normally be able to pull it without authentication. If the issue persists, check whether the package has public visibility and whether anonymous pulls are working. You can also try pulling it again after logging in to see if the error changes. |
Run
docker logout ghcr.io.The 401 from curl is actually normal: the Docker registry v2 spec always returns a 401 challenge so the client knows to fetch a bearer token from the
realmURL (https://ghcr.io/token). For public images, clients fetch an anonymous token from there.The reason Docker failed with
denied: deniedis that you have stale or expired credentials saved forghcr.ioin~/.docker/config.json. Docker automatically sends those saved credentials instead of pulling anonymously, and GHCR rejects them. Once you log out, the pull succeeds anonymously.