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,414,272
Community Members
 
Community Events
170
Community Groups

using self signed certificate in bitbucket-pipelines.yml

Hi All,

I want to use a private repository to store docker images. Unfortunately it has self signed certificate only.  How can I accept this certificate in my bitbucket-pipelines.yml? 

In gitlab there is an opportunity to set parameters for docker service like this: 

services:                                                                                                                                          
 - name: docker:dind                       
         command: ["--insecure-registry=fqdn_of_registry:port"]  

Is there a similar method in bitbucket? 

1 answer

0 votes

Hi Zamek,

Try following the instructions here: https://docs.docker.com/registry/insecure/#use-self-signed-certificates

There may be some additional configuration required, so let me know how it goes. At the moment we don't allow setting Docker daemon flags, but those instructions don't appear to require changing any flags.

 

Thanks,

Phil

Hi Philip,

I could implement self signed certificate handling in gitlab. I think so it is very important, because most of the users doesn't have a certified server.  AFAIK docker daemon needs to notify that sites have no signed certificate.  Until my bitbucket-pipelines.yml entering to a stages, docker daemon already started. Is there any other method, to notify daemon insecure sites? 

 

thx,

Zamek

Hi Zemek,

Unfortunately not, for the time being.

I see you've already started following the related feature request for this. So, I'd say that's the best place to watch for updates on us adding support.

Thanks,

Phil

Hi Philip,

Yes, thanks I found it later. 

thx,

Zamek

any updates on this.. i don't need an insecure route but a self signed ssl cert should be configable with bitbucket pipeline's docker.

Like Danny Thuering likes this

Has anyone figured out how to connect to a self-signed Docker registry with basic authentication via Bitbucket Pipelines? The Docker documentation says that in some cases you must restart Docker for changes to take effect. How do you restart the Docker service provided by Bitbucket? It's not listed as a service (`service --status-all`) AFAIK.

Edit: after seeing a similar post, https://community.atlassian.com/t5/Bitbucket-questions/How-to-configure-docker-daemon-with-pipelines-to-trust-a-private/qaq-p/758893, I realize I can't restart BB's Docker.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events