-
I pushed docker image to my public repo. from other computer, I tried to pull, and got -no basic auth credentials- error Do I have to login even for pulling public images ? docker pull docker.pkg.github.com/xmlking/micro-starter-kit/account-srv:v0.1.1 |
Beta Was this translation helpful? Give feedback.
Replies: 19 comments
-
Yes, at present you do need to authenticate to read even publicly available packages. |
Beta Was this translation helpful? Give feedback.
-
How would I go about referencing a GitHub registry hosted docker package within an
|
Beta Was this translation helpful? Give feedback.
-
Hi, got the same issue, even if I authenticate, here is my yml file content:
I can successfully publish image to registry, but can’t pull it in step ‘Pull Docker image’. Am I missing something? Thanks |
Beta Was this translation helpful? Give feedback.
-
Hi, Is this a bug? For public images, the layers can be downloaded from the GUI without login. |
Beta Was this translation helpful? Give feedback.
-
This makes it very hard to use the public registry, it’ll need to not require auth if you want any real adoptation. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
This. Completely this. The lack of public non-auth pulls is killing any sort of “draw” to GitHub Packages… |
Beta Was this translation helpful? Give feedback.
-
Is it planned that this will change? |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
You’re right. And for this purpose I did a workaround you can use to publish your freshly built docker images to Dockerhub. |
Beta Was this translation helpful? Give feedback.
-
@ethomson do you have any way to follow along with the issue? A ticket or something? |
Beta Was this translation helpful? Give feedback.
-
GitLab Docker registry does not require authentication for public projects. https://docs.gitlab.com/ee/user/packages/container_registry/index.html#using-with-private-projects |
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
-
Any news on this. It is kind of a big issue. |
Beta Was this translation helpful? Give feedback.
-
i just tried this feature. Why is it called public docker registry if you need authentication AND permissions ? Second … well it would be nice if we could publicly read from a public docker registry ? |
Beta Was this translation helpful? Give feedback.
-
Any news on this, please? |
Beta Was this translation helpful? Give feedback.
Yes, at present you do need to authenticate to read even publicly available packages.