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

Your Points Tracker
  • 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
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?
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

What docker version is Bitbucket Pipelines running?

For my automated tests on a C project I'm working on, I'm trying to run the sanitizer (-fsanitize=address) with debug mode enabled. However this fails since today with this message:

==513==LeakSanitizer has encountered a fatal error.
==513==HINT: LeakSanitizer does not work under ptrace (strace, gdb, etc)

On my local machine with Docker version 19.03.4, this error doesn't occur.

What docker version is Bitbucket Pipelines running? Was the version changed recently? I was running the pipeline perfectly fine for months and this happened today.

2 answers

Hi @Gavriil

BitBucket Pipelines has been using docker version 18.09.1 since Jan 2019.

You can verify it by using this step:

- step
- docker
- docker version

Docker version upgrade is currently on our planned roadmap. You can vote on this page so we may prioritise the work.



Hi @Tung Tran

Perhaps you have already considered this, but just in case - the specific issue affecting LeakSanitizer can be addressed by running docker with the option

--cap-add SYS_PTRACE

Perhaps this could be applied as a quick fix, without waiting for the docker version upgrade?

Like Gavriil likes this

@Stephen ProcterThanks Stephen, indeed this was the fix we implemented.

@Gavriil - when you say you implemented that fix, do you mean there is some way of setting the --cap-add SYS_PTRACE option on the Docker instance running inside Bitbucket Pipelines? If so I would love to know how to do that!

Like nathan likes this

@Stephen ProcterSorry for the confusion. I meant that adding that argument (cap-add)

for local testing was indeed the fix, but for our build process on Bitbucket pipelines we implemented a workaround: we disabled the debug mode when the sanitizer was enabled before running the tests. Then we re-enabled it later before running Valgrind.

Screenshot from 2020-09-14 09-43-15.png

Like nathan likes this

+1 - I can't find anywhere in the documentation that shows where you can add a custom command line arg to the docker invocation for the build image in your pipelines file.

sorry, meant to post this as a reply to Stephen's comment above...looks like there's nowhere in the UI to delete this "answer" and repost as a comment.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket Pipelines

Bitbucket Pipelines Runners is now in open beta

We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...

518 views 10 8
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