Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,465,032
Community Members
 
Community Events
176
Community Groups

pipe.yml - private docker registry

Edited

Hello,

 

I am trying to understand how the customized pipelines works. Ther problem I am facing is that I am unable to set the access credentials to access my private docker registry in the pipe.yml file.

I have my pipe build in a `pipeline-alfa` repository. The pipe.yml contains:

name: My pipeline-alfa
image:
name: registry.my-registry.com/pipeline-alfa:latest
username: basic-auth-user
password: ***basic-auth-pass****
email: user@foo.com
category: Utilities
description: Showing how easy is to make pipes for Bitbucket Pipelines.
variables:
- name: ENV_NAME
default: ‘myProduction’
repository: https://bitbucket.org/foo/pipeline-alfa
maintainer:
name: user
website: https://foo.com
email: contact@foo.com
vendor:
name: Demo
website: https://example.com/
email: contact@example.com
tags:
- helloworld
- example

I am running this pipeline from my `repository-main` as follows:

...
'**':
- step:
script:
- pipe: foo/pipeline-alfa:1.0.6

I can see that this work as expected. The pipe.yml from the pipeline-alfa repository is picked and on my private docker registry host I  can see (nignx access log):


xx.xx.xx.xx - - [27/Jul/2022:19:15:02 -0400] "GET /v2/ HTTP/1.1" 401 188 "-" "docker/20.10.15 go/go1.17.9 git-commit/4122ba1 kernel/5.10.101 os/linux arch/amd64 UpstreamClient(Docker-Client/20.10.15 \x5C(linux\x5C))"

bitbucket pipeline run log is saying:

...
Unable to find image 'registry.my-registry.com/pipeline-alfa:latest' locally

docker: Error response from daemon: Head "https://registry.my-registry.com/v2/pipeline-alfa/manifests/latest": no basic auth credentials.
See 'docker run --help'.

- Why username and password are not provided for the docker registry?

- Are the private registries not supported?

Related documents:

https://support.atlassian.com/bitbucket-cloud/docs/use-docker-images-as-build-environments/

https://support.atlassian.com/bitbucket-cloud/docs/write-a-pipe-for-bitbucket-pipelines/

 

 

1 answer

0 votes

Hi @szumak,

I'm afraid that private Docker images are not supported in pipes, the image needs to be public.

This is also mentioned in our doc

You don't have to use Dockerhub, if you have another service to host Docker images, but the image does have to be public.

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events