According to the documentation at:
With a self-hosted runner you can use a custom docker-in-docker service.
"The 'services' section in your bitbucket-pipelines.yml file contains a custom docker service. Remove 'image', 'variables' and 'environment' from the docker service definition or use a self-hosted runner for the step."
name: Build Deploy rev-proxy
- ping localhost -c 1
The runs-on parameter in the yaml file must contain a label named self.hosted. I believe that culprit here is that your yaml file has only the mylocalrunner label, so Pipelines doesn't see that step as a step that will run on your local runner.
You can modify the runs-on parameter as follows:
and this should allow the step to run on your runner. The label mylocalrunner should also exist on the runner you configured on Bitbucket website either from the repository settings or from the workspace settings.
Please feel free to let me know how it goes and if you have any questions!
Hi, Bitbucket community! Are you a DevOps practitioner (or know one in your network)? Do you have DevOps tips, tricks, or learnings you'd like to share with the community? If so, we'd love to hea...
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