Custom resource image unable to be pulled from ECR

#1

Hi,

We are currently investigating Concourse and have created a custom resource type. We are wanting to store this image in ECR as our AWS is not allowed any external connections.

Unfortunately, Concourse will not pull a resource type image from ECR. Has anybody else hit this problem and found a way to resolve it?

0 Likes

#2

You should be able to set something like

repository: <aws_account_id>.dkr.ecr.<region>.amazonaws.com/<image>:tag

in the source of the resource type. It’s essentially just a standard docker image resource config.

What kind of error are you seeing?

0 Likes

#3

I was having the same problem, but found I needed to use: privileged: true in the task and then I got further with it.

0 Likes

#4

Thanks, turned out I was doing something stupid that I’d blamed on Concourse/ECR.

A combination of tagging and making it privileged has done the trick.

0 Likes