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
We're looking at running jobs in Docker containers as opposed to in the agent environment. While it seems pretty easy to set up, I can't see any option for adding credentials for a private repository.
Is it possible to use Docker images from a private repository?
If not, I'd like to feed back that this feature is pretty useless. Most images on Docker hub run as a non-privileged user, meaning that we would not be able to install required packages (such as jq, Octo, and many, many more). To be honest, even if we could install those tools prior to building, having to do it every time would add far more overhead to the Bamboo server in terms of both time and bandwidth.
Unfortunately this is indeed not yet supported - please watch and vote for the following issue to increase Atlassian's priority for closing this notable gap:
Please note that the workaround listed there has been discussed in more detail in how to configure docker runner to authorize with private docker registry, so if your happen to target the Amazon Elastic Container Registry, the last comment by Stephen Leavitt points out that this special case can be nicely addressed via the Amazon ECR Docker Credential Helper meanwhile.
Thanks for your reply,
It's quite disappointing to see that Bamboo have marked this as low priority in the issue you linked and are not actively working to add this vital feature, especially given the rise in rise in popularity of containerisation.
I have added my vote, fingers crossed other do to.