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
Thanks for your efforts that PAUSE_IMAGE, AUTH_PROXY_IMAGE, and CLONE_IMAGE are provided to support custom Docker registry in the self-hosted runner. Is it possible to support overriding docker-daemon image (ie. docker-public.packages.atlassian.com/sox/atlassian/bitbucket-pipelines-docker-daemon:v20.10.18-prod-stable) as well?
Here are the use cases:
(1) The firewall blocks the traffic between our internal environment and docker-public.packages.atlassian.com. So we have to use an internal docker registry for remote docker registry mirror/cache and override the docker image on our internal registry mirror.
(2) We has built our custom docker daemon for most cases in our internal environment. At the moment, for each pipeline which has enabled docker service, we have to define the following docker service in the pipeline.yaml. If overriding docker-daemon image is supported, we may configure our <internal-docker-registry>/<custom-bitbucket-pipelines-docker-daemon> as the default docker daemon, so we could remove the following code from each pipeline and therefore the pipeline.yaml becomes simpler and easier to understand for our developers.
NO_PROXY: $NO_PROXY. 2
Hi Aqsa and welcome to the community!
There is a feature request in our issue tracker with the exact same use case you posted here:
You can add your vote to that ticket (by selecting the Vote for this issue link) as the number of votes helps the development team and product managers better understand the demand for new features. You are more than welcome to leave any feedback, and you can also add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to get notified via email on updates.
Implementation of new features is done as per our policy here and any updates will be posted in the feature request.