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

Docker container run, container removed before it is started



I'm using a Docker task in a Bamboo (7.0.2) plan and running the "run a docker container" option.

It looks like my container is either taking too long for Bamboo to see it as a succesful start or maybe no proper return code (?) because the container is removed straight after the execution of the plan.

I tried to introduce a "wait for service" but I don't really have something to check against so even though the container is then started correctly, the plan will still fail and remove the container.

When I just use a script task and execute the same run, all is fine. This looks like a shortcoming in the Docker tasks.

I would like to use the out of the box tooling so if anyone has a suggestion, it's very welcome! Otherwise I'll stick to a script task.




1 answer

0 votes
Bloompeak Support
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Jun 29, 2020

I suggest that you stick to script task because it is under your control and transparent whereas docker task is a black box. In case something goes wrong, there is no hint for the reason of the failure.

Thanks for your answer, that's what I'm doing now. Still would be nice to have the plugin working properly, else why even bother making plugins? I could just script everything.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events