Can this be changed please? There is no good reason to make this be the case as you can download from the site even without login. This blocks all kinds of third party CI services from working as often you can not specify registry credentials for those.
Can this limitation be written with bold letters in the documentation becuase it makes GitHub Package Registry not usable for any open source projects at the moment.
Are there any plans on removing this requirement? Currently it is not possible for us to use the docker registry in any of our projects. This was one of the main reasons we thought we could use GitHub.
This. Completely this. The lack of public non-auth pulls is killing any sort of “draw” to GitHub Packages…
Is it planned that this will change?
Thanks for the feedback. We realize that this is a popular feature request, and we’ve passed it along to the GitHub Package Registry team.
Any update on this? I’d love to have everything live on GitHub, but without being able to pull the image without logging in, I’m going to have to publish to Docker Hub instead.
You’re right. And for this purpose I did a workaround you can use to publish your freshly built docker images to Dockerhub.
this is a fork of a fork of a github action (without release currently).
It builds and publishes docker images to GPR except you use the param
Maybe that helps until Github comes up with a solution.
@ethomson do you have any way to follow along with the issue? A ticket or something?
GitLab Docker registry does not require authentication for public projects.
This is a problem I ran into when trying to make an action that runs a script in a container that I have published to GitHub Package Registry. Unfortunately it fails on the
FROM statement because authentication is required, making Package Registry unuseable as a place to provide the base layer for a Docker action.
Any news on this. It is kind of a big issue.
i just tried this feature.
I have to say i am disapointed first for the lack of transparency. Yes there are tutorials on how to login, but then again all public repositories support unauthenticated downloads.
Why is it called public docker registry if you need authentication AND permissions ?
So please first fix the documentation. You need to specify this very clear from the begining. Maybe even change the feature’s name. Private docker registry. Private packages.
Second … well it would be nice if we could publicly read from a public docker registry ?
- Push -
Any news on this, please?
Any update about this issue??
Any news on this?
Any update on this? Really need this feature
Any news on this? Just spent half a day trying out to built an automated workflow for this and found out that you need to authenticate!
It’s really bad that it is not transparently mentioned and that it works this way !
Any news on this, please?