Details
-
Suggestion
-
Resolution: Duplicate
Description
Right now Bitbucket Pipes doesn't support own private registries, only Docker Hub.
In some cases it's really useful to use own private images on AWS ECR or Container Registry on Google Cloud with some software that you don't want to share.
I propose to add ability to define credentials for docker registry in similar way as we have for image:
Example 1 - Docker Hub:
#!yml
- pipe: account-name/openjdk:8
username: $DOCKER_HUB_USERNAME
password: $DOCKER_HUB_PASSWORD
email: $DOCKER_HUB_EMAIL
variables:
AWS_ACCESS_KEY_ID: '<string>'
AWS_SECRET_ACCESS_KEY: '<string>'
AWS_DEFAULT_REGION: '<string>'
APPLICATION_NAME: '<string>'
Example 2 - AWS ECR:
#!yml
- pipe: <aws_account_id>.dkr.ecr.<region>.amazonaws.com/openjdk:8
aws:
access-key: $AWS_ACCESS_KEY
secret-key: $AWS_SECRET_KEY
variables:
AWS_ACCESS_KEY_ID: '<string>'
AWS_SECRET_ACCESS_KEY: '<string>'
AWS_DEFAULT_REGION: '<string>'
APPLICATION_NAME: '<string>'
Example 3 - Google Container Registry:
#!yml
- pipe: <region>.gcr.io/<project>/image:latest
username: _json_key
password: '$GCR_JSON_KEY'
variables:
AWS_ACCESS_KEY_ID: '<string>'
AWS_SECRET_ACCESS_KEY: '<string>'
AWS_DEFAULT_REGION: '<string>'
APPLICATION_NAME: '<string>'
Example 4 - other registries:
#!yml
- pipe: docker.your-company-name.com/account-name/openjdk:8
username: $USERNAME
password: $PASSWORD
email: $EMAIL
variables:
AWS_ACCESS_KEY_ID: '<string>'
AWS_SECRET_ACCESS_KEY: '<string>'
AWS_DEFAULT_REGION: '<string>'
APPLICATION_NAME: '<string>'