How do I get Cloud Pipelines to authenticate with crg.apkg.io to retrieve the docker images I built?

[NB]

I have created a package registry in bitbucket within the repository that hosts the Dockerfile, and have pushed images with the appropriate semver tags as I've seen fit to do so (in the same way I have done publicly on hub.docker.com)

In my local development environment, I can `docker login` and pull those images fine and, by extension, can use those images in my docker-compose orchestrations.

However, as soon as I use these same images in a bitbucket-pipelines.yml file for any other repository in my workspace, I am receiving an authentication error, presumably because the bitbucket host has no way of... well, authenticating.

What would be the process? The documentation contains no guidance.

[Mark C]

Hi @NB

Thank you for reaching out to the community.

You can actually use your API token and Atlassian email as your credentials when using the image in your Pipelines build step.

Here's an example usage:

        image:
          name: crg.apkg.io/SOME_PACKAGE_NAME:VERSION
          username: $ATLASSIAN_EMAIL
          password: $API_TOKEN
          email: $ATLASSIAN_EMAIL

Regards,
Mark C