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:
docker:
image: docker:dind
environment:
HTTP_PROXY: "http://username:password@proxy2.domain.com"
HTTPS_PROXY: "http://username:password@proxy2.domain.com"
"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:latest
pipelines:
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
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.