Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


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!


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
Community Members
Community Events
Community Groups

Problem starting docker bamboo-agent with DC bamboo server

Hi all,

I'm running the data-center versions of bamboo-server (6.9.1) and bamboo-agent (6.9.1).  I've been through the documentation and I have the helm charts setup correctly as far as I can tell on both the server and agent side.  However, when I try to start the bamboo agent, the bamboo-agent crashes immediately and the following message is the only line in the agent logs: "Please run the Docker image with Bamboo URL as the first argument".  The bamboo server is defined in the agent's helm chart, so I am confused on where to go from here.  I haven't had much luck finding others with this problem.  Any thoughts?

1 answer

1 accepted

@Nicolas Grossi   Thanks.  Took a look at that page.  That prompted some thoughts and I have some more information:

I am using the latest version (1.11.0) of the helm charts from here:

When I try to deploy the images via helm, I get the messaged from above.  When I deploy with kubecltl run and specify the BAMBOO_SERVER as the argument, then the agent is able to start.  I first executed the kubectl run with the local cluster dns name and got failure in name resolution.  I then tried the IP address and the bamboo-agent then connected, but ran into another error.  However, our goal is to deploy this using helm so I feel that I can at least say now that helm isn't correctly starting the image.  I'm currently looking at how helm passes in arguments to the image when its is attempting to deploy/start the image. 

Like Nicolas Grossi likes this
Eduardo Alvarenga
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 10, 2023

Hello @William McKeon

Try using an updated Bamboo version from 8.0 and onwards. Helm charts were released after 6.9.1 was available, and the current docker container bootstrap instructions are designed to interact with recent Bamboo releases and may not work with older versions.

Bamboo 6.9.1 has reached its End-of-life. Atlassian does not support instances on versions that have reached their End of Life. The only exception is for assistance related to upgrading from your EOL version to a supported version.


Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful-- 

Like Nicolas Grossi likes this

@Eduardo Alvarenga @Nicolas Grossi Thanks for the help.  Really appreciate it.  Marking as accepted.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events