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 was hoping to open an issue at jira.atlassian.com for Bamboo, and while I can see issues there, it does not allow me to select Bamboo as the product to open an issue against.
I was hoping to have the Spotify Docker client updated in a future release so it doesn't have to be done manually. docker-client-8.10.1-shaded.jar (which ships with Bamboo 6.6.1) appears to have partial/incomplete/broken support for outbound access through an HTTP proxy (Constantly receive "Expected authority at index 7: http://" error message when using Docker push/pull tasks), and this seems to be solved by using docker-client-8.11.7-shaded.jar (and appropriate entry with correct MD5 sum in atlassian-bamboo/WEB-INF/classes/hash-registry.properties). The changelog up to 8.10.1 shows fixes for HTTP proxy, but 8.11.2 and 8.11.3 show further proxy fixes as well that appear to address the issues. It would be nice if future releases did not require manually updating this JAR file to get full HTTP Proxy functionality with the Spotify Docker client.
I'd happily open an issue in jira.atlassian.com for this if it would let me select Bamboo as a product :)
Thank you for your report.
There are 2 channels you can use to report problems with Bamboo, one is this very page second is Atlassian Support.
I opened a new bug to track the Docker issue: https://jira.atlassian.com/browse/BAM-19987