How can I access pipes that are deployed in AWS ECR

[brianrook]

We're using AWS ECR to store our private images.  We've figured out how to access our images in a BB pipeline, however, I haven't figured out how to access a pipe in ECR yet.  

When I execute my pipeline, I get an error about being unable to find the pipe:

- step:
    name: "Checkout and deploy our update"
    script:
      - pipe: 5...r.ecr.us....amazonaws.com/pipes/update-staging-pipe:1.0.0

error:

Configuration error

It looks like you tried to use a pipe in your bitbucket-pipelines.yml that doesn’t exist. Check the name of the pipe and try again.

In order to solve our issue with private docker images on the build we added some AWS credential configuration:

from bitbucket-pipelines.yml:

image:
    name: 5...r.ecr.us....amazonaws.com/devops/bbp-helm:test
    aws:
        access-key: $AWS_ACCESS_KEY_ID
        secret-key: $AWS_SECRET_ACCESS_KEY

Is there a similar configuration on the pipe element that we can use to access our pipe image in ECR? 

[Raul Gomis · Accepted solution]

Hey @brianrook ,

If you are referencing the docker image directly you will need to use docker://:

- step:
    name: "Checkout and deploy our update"
    script:
      - pipe: docker://5...r.ecr.us....amazonaws.com/pipes/update-staging-pipe:1.0.0

Bear in mind that we only support public docker images for now. If you need support for private images you can vote and comment with your use case here: https://bitbucket.org/site/master/issues/18270/use-private-docker-images-as-pipes so that we can gauge the interest on it.

Regards,

Raul

[Taylor Gregory]

Can we make this more explicit in the documentation?

EDIT:

Just to be clear, I know that it shows the docker:// prefix in  the documentation. It doesn't specify that it must be there for ALL public docker images; not just ones on Dockerhub.

I had an image public on GCP artifact registry and was trying things like gcp://...doh!!