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

Not seeing logs when running a pipeline via local runner

I am using a Bitbucket pipeline that runs on a local runner instance. Regardless if the pipeline succeeds or fails I do not see logs from the runner on the Bitbucket Pipelines interface. Looking on the host where the local runner is hosted I see via "docker logs -f build" that log entries are getting generated. I would expect that these log entries are made available on the Bitbucket UI side. 

The attached screenshot shows what I am seeing.


Screenshot 2021-06-06 at 18-05-55 isotonteam isoton-api Pipelines — Bitbucket.png


My "bitbucket-pipelines.yml" file:

name: Ansible deployment
runs-on: chef
image: tvarga/ansible:2
ansible-playbook -i runner hello_world.yml
sleep 15

"docker logs -f build" displays the following - which I would expect to the see in the above screenshot.


+ id
uid=0(root) gid=0(root) groups=0(root)
+ ansible-playbook -i runner hello_world.yml
PLAY [This is a hello-world example] *******************************************
TASK [Gathering Facts] *********************************************************
ok: [test-host]
TASK [Create a file called '/tmp/testfile.txt' with the content 'hello world'.] ***
changed: [test-host]
PLAY RECAP *********************************************************************
test-host : ok=2 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
+ sleep 15

1 answer

Any updates on this?

Suggest an answer

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

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

3,449 views 3 10
Read article

Atlassian Community Events