According to the documentation at: https://support.atlassian.com/bitbucket-cloud/docs/pipelines-runners-frequently-asked-questions/
With a self-hosted runner you can use a custom docker-in-docker service.
services:<br>docker:<br>image: docker:dind<br>environment:<br>HTTP_PROXY: "<a href="http://username:password@proxy2.domain.com" rel="noopener nofollow noreferrer" target="_blank">http://username:password@proxy2.domain.com</a>"<br>HTTPS_PROXY: "<a href="http://username:password@proxy2.domain.com" rel="noopener nofollow noreferrer" target="_blank">http://username:password@proxy2.domain.com</a>"
"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."
definitions: services: docker: image: docker:dind environment: HTTP_PROXY: "http://localhost" HTTPS_PROXY: "https://localhost"image: alpine:latestpipelines: branches: main: - step: name: Build Deploy rev-proxy runs-on: mylocalrunner script: - ping localhost -c 1 services: - docker
Hi Rafael,
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:
runs-on: - self.hosted - mylocalrunner
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!
Kind regards,Theodora
It looks like you're new here. Sign in or register to get started.