Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to use a shared Dockerfile in the Docker task

In bamboo, I have created 2 stages. In the first one, I check out the source code and compile it. I've also created an artifact that is the Dockerfile located in the checked out directory and shared it. In the second stage, I've defined an artifact dependency which is the artifact I've created earlier in the previous stage.  For the destination directory, I've specified ../CAS-CR-JOB1/download-data/.  I've chosen the "Use an existing Dockerfile located in the task's working directory" option to make my intention clear that I want to use the shared Dockerfile. But I get "no such file or directory" when I run the plan.

To be honest, I doubt that the "Use an existing Dockerfile located in the task's working directory" should enable using the shared artifact, because the artifact is in the donor job's build directory. I can verify this by running the ls command. It shows an empty list. But if I try 'ls ../CAS-CR-JOB1/download-data' I get the Dockerfile listed.

So how would I use the Dockerfile produced from the previous stage and build that? What am I doing wrong?

1 answer

1 accepted

0 votes
Answer accepted

It turns out that if I want to have the shared artifact available in the current jobs working directory, then when creating the artifact dependency, in the Destination directory field I should write ".". After I did that, the problem got fixed.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

223 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you