Registry changes tag ID between push and pull
I really don't know how to explain what is happening, so I'll just describe what I'm seeing.
I have a project that builds a Docker image and pushes it to the GitLab registry.
https://gitlab.com/demo-clusters/gcloud-kubectl-helm
I have another project that uses that Docker image in its CI/CD pipeline
https://gitlab.com/demo-clusters/i2p.online
The problem is that when the first project pushes the image to the registry, the log shows a certain SHA for the image: https://gitlab.com/demo-clusters/gcloud-kubectl-helm/-/jobs/50608858
But the registry shows a different SHA: https://gitlab.com/demo-clusters/gcloud-kubectl-helm/container_registry
And when consumed by the second project, the log shows the SHA for the pulled image: https://gitlab.com/demo-clusters/i2p.online/-/jobs/50610255
And that SHA matches the shortened SHA shown by the registry, but does not match the SHA of the pushed image.
It's also strange that I can't find that SHA in the logs of any of the builds of the project, so I have no idea where it's coming from.
If I pull locally, I see the original SHA again.
It's as if the container registry view and runner output are using a different type of ID for the same image.
Note that the downloaded image is actually the correct one. I'm just confused about the IDs.