You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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:
- name: docker:dind
Is there a similar method in bitbucket?
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.
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?
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.