How to use private registry for bitbucket pipe

[Mohammad Imran Ansari]

I want to write the bitbucket pipe and store it in my custom private registry how can i do it. I see in the comments it says we can only store it in Docker Hub. 

[Patrik S]

Hello @Mohammad Imran Ansari and thank you for reaching out to Community!

I'm afraid that pipes currently do not natively support the usage of private docker images, and we already have an open feature request to implement this functionality : 

• https://jira.atlassian.com/browse/BCLOUD-18270

We encourage you to add your Vote there to give this feature traction and help the product managers understand the interest. Also, you have the option to Start Watching that ticket to be notified whenever there's any update.

Below is an example workaround if you want to use a private image store in DockerHub, where you can use the syntax docker://<repository-name>/<image-name>:<tag> to reference the pipe : 

pipelines:  
  default:    
    - step:
        script:
          - echo $DOCKER_PASSWORD | docker login -u $DOCKER_USER --password-stdin                         
          - pipe: docker://<my-private-image-repository>/<my-private-pipe>:<tag>            
            variables:
              MY_VARIABLE: 'foo'
              MY_OTHER_VARIABLE: 'bar'

It's important to execute the docker login before the pipe's execution, so it will have access to the private images.

In that feature's comments, you can find some other suggested workarounds to use private images as pipes that might be helpful for your use case, depending on the registry you are using : 

• AWS ECR private images
• Using insecure custom registry (only available with self-hosted runners)

Hope that helps! Let me know in case you have any questions.

Thank you, @Mohammad Imran Ansari !

Patrik S