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

Bamboo-server official docker image issues



We've been running Bamboo-server for a while now as a docker container and have just recently upgraded to 7 ( and have a few questions regarding the official docker image / Dockerfile (


- Where can i post PR's / issues for the official image? (thus my question here)

- Currently the Apache Tomcat Native library is installed but seems to be in the wrong location with (atleast the `atlassian/bamboo-server:7` image, as it cant be found in the JAVA class path:  

25-Mar-2020 13:07:40.539 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib]

- Currently we're also using it behind a reverse proxy, but unlike the other official images (i.e. atlassian/crowd) it doesnt support the ATL_PROXY*-environment variables. Is there a roadmap to include this? For now we have to build our own image just to `alter` the `/opt/atlassian/bamboo/conf/server.xml`-file to map to the correct ports et al.


- The official image on the Docker hub ( also seems to be dynamically built from the source, however the Dockerfile as visible there ( doesnt reflect the current state of the image... Also due to the fact that images are being rebuilt periodically, the tags aren't in a usefull order ( as finding out if there is a newer 7-image, one would have to flick through the tags manually... (searching for `7` still leaves a lot of hits... ) Is there a plan to implement the tag-information as with the `official` images (i.e. etc etc) They include a list of most frequently used tags right on the README ...



1 answer

No answers or even a sort of notice... Typical atlassian

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events