Bitbucket Pipelines Runner

Self-hosted Bitbucket Pipelines runner for Unraid that executes pipeline step containers locally via the Docker socket with an outbound-only network connection.

  • Development
  • Other
Self-hosted Bitbucket Pipelines runner for Unraid that executes pipeline step containers locally via the Docker socket with an outbound-only network connection.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

65/100 Good

Maintained
88last commit 26 days ago
Popular
4094 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
78no serious findings, CI, tests, OpenSSF Scorecard 4.4/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 23 days ago

GitHub stars
94
Open issues
6
Last commit
2026-10-26
Latest release
0.6.3
License
MIT
Activity
rising

Checked 23 days ago - source: GitHub (mathieu-lemay/pipeline-runner)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Docker Runner Setup This runner executes pipeline steps as Docker containers on the host using the Docker socket. Follow Atlassian's Linux Docker runner guide to configure your environment, and ensure the runner has outbound-only network access. source

Fetched 47 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I install the runner and start a pipeline run?

Install it with pipx install bitbucket-pipeline-runner. Then change into the repository directory and run pipeline-runner run to execute a pipeline.

Where are pipeline artifacts, logs, and caches stored?

Artifacts and execution logs are stored in the user data directory, such as ~/.local/share/pipeline-runner on Linux or ~/Library/Application Support/pipeline-runner on macOS. Caches are stored in the user cache directory, while Docker cache is stored in a Docker volume.

How can a pipeline step clone from a private Git repository over SSH?

Run the pipeline with the --ssh flag to expose your SSH agent to the step container. If the agent has multiple keys, the key required by the target Git host should be first.

How do I force an amd64 pipeline container on Apple Silicon?

Set PIPELINE_RUNNER_DOCKER_PLATFORM to the target platform to affect only the pipeline container. To force all containers, set DOCKER_DEFAULT_PLATFORM, though the feature is still experimental.

Does the Docker-based runner need inbound ports or a reverse proxy?

The Docker runner executes pipeline steps as Docker containers on the host using the Docker socket. The setup guidance says to ensure the runner has outbound-only network access.

What security concern is associated with Docker-socket-based self-hosted runners?

Docker-socket-mounting runners can be insecure in environments with strict compliance requirements.

Answers sourced from github.com, support.atlassian.com, www.reddit.com

Community

Collected 47 days ago - public community threads