K
Q

Concourse tries to pull docker image using wrong sha256 digest and fails

4/25/2018

I am running Concourse 3.10.0, which I installed with the official helm chart, on GKE. I am getting this error, which refers to the wrong sha256:

Pulling registry.hub.docker.com/linkyard/concourse-helm-release@sha256:c47e868ec58fcf81b3b0d597bd10a91fc1908da4c13561e7834584997d1fcb9d...
Error response from daemon: pull access denied for registry.hub.docker.com/linkyard/concourse-helm-release, repository does not exist or may require 'docker login'

If I run docker pull linkyard/concourse-helm-resource:2.8.2-3 locally, it works, but downloads a different sha256.

It looks to me like I have run into issue 33 in concourse's docker-image-resource plugin, but that was fixed 2 years ago.

I had a little look at the Concourse Dockerfile and the helm chart, but I couldn't figure out how docker-image-resource gets included into the Concourse deployment.

How can I upgrade docker-image-resource to see if that fixes this bug?

-- Robin Green
concourse
dockerfile
google-kubernetes-engine
kubernetes-helm

Similar Questions

GCE Ingress not picking up health check from readiness probe
Kubernetes: TLS on an Ingress; hosts using wrong certificate
error: You must be logged in to the server - the server has asked for the client to provide credentials - "kubectl logs" command gives error
mounting a directory for pods in kubernetes
Kind Kubernetes cluster doesn't have container logs

1 Answer

5/12/2018

This was actually just a simple typo - concourse-helm-release instead of concourse-helm-resource - but the error messages were misleading.

For future reference, the docker-image-resource is baked into the Concourse docker image by BOSH, and the relevant version can be found in this file.

-- Robin Green
Source: StackOverflow