Self-hosted runner ECR OIDC/ApiKeys Queued

[Roberto Silva]

Good morning,

I'm having a problem when I try to setup a build step on a self hosted runner running on docker.

I'm trying to pull an ECR image from my aws account with:

image:

name: XXXX.dkr.ecr.eu-central-1.amazonaws.com/image:version

aws:

  access-key: $AWS_ACCESS_KEY

  secret-key: $AWS_SECRET_KEY

but the job remains queued and is not executed.

It also happens with OIDC setup:

image:

name: XXXX.dkr.ecr.eu-central-1.amazonaws.com/image:version

aws:

   oidc-role: $AWS_OIDC_ROLE_ARN

If i change the image to a public one, it works without problem on the self-hosted runner.

Is there any bug with this setup?

[Mark C]

Hi @Roberto Silva,

Welcome to the community.

Would you be able to confirm if the private image is accessible locally?
Also, could you confirm as well if Bitbucket Cloud Pipelines is allowed to pull the image?

Regards,
Mark C