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,556,459
Community Members
 
Community Events
184
Community Groups

Bamboo Agent in docker container is not recognized by Bamboo Server

Bamboo server is installed in a docker container, I need add any Bamboo agents as docker container too, and then I make what this guide say Getting started with Docker and Bamboo.

Server is runnig in 192.168.1.15:8085 and remote agent support is enabled, then I run Bambo docker container as follow:

 

$docker run -e HOME=/root/ -e BAMBOO_SERVER=http://192.168.1.15:8085 -i -t atlassian/bamboo-java-agent

 

but I get in Online remote agent tab:

 

There are currently no online remote agents configured on this Bamboo instance.

 

and below:

Jan 15, 2016 3:09:30 PM A remote agent is loading on 77524df60fda (172.17.0.1).

 

How can I make Bamboo server recognize agents?

 

Note:Bamboo server is a trial

3 answers

Got it solved by updating Broker URL and Broker Client URL to hold the private IPs being used within VPC.

Also updated the IP for agent at bamboo-agent-home/conf/wrapper.conf

Could you please give details about the resolution you implemented on this.

Have this very same issue.

Tried alot but not resolved yet.

Still working to get it up-and-running. :) 

I have the same issue. I wonder if docker agents are being seen as remote since they are not accessing the server via localhost. I would love some official clarification.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events