Cannot pull docker image from Github Package Registry by digest #25632
-
First build, tag and push an image:
then pulling the same image by digest directly:
this works with docker.io as well as other private registries. |
Beta Was this translation helpful? Give feedback.
Replies: 16 comments 1 reply
-
HI @michaelbeaumont, Thank you for being here! We don’t support pulling an image by digest currently, only by tag. Here is a link to our docs: |
Beta Was this translation helpful? Give feedback.
-
Currently means there’s plans to support it in the future? Do you have any updates? |
Beta Was this translation helpful? Give feedback.
-
It would be great to be notified of when that would be available. Due to this, Google Cloud Run is currently not compatible with GitHub Packages. That forces us to use Google’s container registry. |
Beta Was this translation helpful? Give feedback.
-
Hi! Does this mean that github packages’ docker registry cannot be used with docker swarm? When I attempt to (re)-deploy our docker swarm services, which use images hosted on our package registry, I get this error:
|
Beta Was this translation helpful? Give feedback.
-
I think this would be a very helpful feature to support. Pulling an image by digest allows you to be very precise about the specific deployment you want. The lack of this feature also means the github registry isn’t compatible with a number of existing tools that assume pulling by digest is possible. |
Beta Was this translation helpful? Give feedback.
-
I beleive this is the underlying cause of incompatibilities such as portainer/portainer#3192 |
Beta Was this translation helpful? Give feedback.
-
Adding on - this makes the Github Package Registry noncompliant with the OCI Distribution spec, and is making buildpacks/pack unable to support publishing to GPR, as mentioned here. Are there any updates on a timeline for this? |
Beta Was this translation helpful? Give feedback.
-
This makes the GitHub Docker Registry almost useless. |
Beta Was this translation helpful? Give feedback.
-
👋 As noted here in the containerd issue our Docker service doesn’t currently support pulling by digest. However we have a new service under private beta which does support pull by digest. The new service also supports the OCI spec which allows for buildpacks etc. Please reach out if you’d like to participate. We have been adding users into the private beta over the past several weeks. |
Beta Was this translation helpful? Give feedback.
-
Hi clarkbw, where do i sign up? |
Beta Was this translation helpful? Give feedback.
-
Email me. The containerd issue has the required info. |
Beta Was this translation helpful? Give feedback.
-
So basically if you deploy with Kubernetes and use digests in logic, you cannot use Github’s Registry. Am I understanding this correctly? |
Beta Was this translation helpful? Give feedback.
-
Hi @iMerica, Yes, you’re understanding correctly. Could you see the comments at the end of this issue and request access to the private Bata? containerd can't pull image from Github Docker Package Registry
Using the new github docker registry containerd kubernetes can't pull image but using docker engine based k8s works fine. Steps to reproduce...
kind/external
|
Beta Was this translation helpful? Give feedback.
-
@clarkbw @iMerica , can you confirm that this new service is active in GitHub Enterprise Server 3.0.4?
|
Beta Was this translation helpful? Give feedback.
-
Correct. @joshbouganim makes a great point. GHE 3.x suffers the same error. The documentation states:
However, while using that tag format and not SHA, the documentation does not indicate that a known, rather alerting docker “warning” (error) will be displayed. |
Beta Was this translation helpful? Give feedback.
-
Is pulling images from the registry by digest available yet? |
Beta Was this translation helpful? Give feedback.
👋 As noted here in the containerd issue our Docker service doesn’t currently support pulling by digest. However we have a new service under private beta which does support pull by digest. The new service also supports the OCI spec which allows for buildpacks etc. Please reach out if you’d like to participate. We have been adding users into the private beta over the past several weeks.