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

Bamboo and jobs in container - is it recommended?

Edited

Hi,

We are starting a new project and we would like to use docker to simplify our build environment (and also simplify production env). 

First of all, we would like to use Docker image of Bamboo, we tested and it works well. But is it recommended to use on such installation option "Run jobs in a docker"? 

It will be docker inside Docker , what is probably not recommended? What are your suggestions and how do you install Bamboo in your building environment?

Regards 

Michal

 

1 answer

0 votes
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 14, 2019

Hi @Michał Szymański

Short answer, you should not use docker inside docker.
I guess this post answers your question:

Please check it out and let me know if you still have questions on this matter.

What are your suggestions and how do you install Bamboo in your building environment?

It really depends on your requirements.

If you are setting it in docker that is because you need some isolation and flexibility to move/replicate the container. There is a performance price to pay, restriction on using docker runner, etc

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events