IF THE PROJECT JUST RUNS IN DOCKER, AUTOMATICALLY DENIED
I HAVE READ .github/CONTRIBUTING.md
Write the sentence: "This project exists to ____."
If the blank doesn't contain Docker, container, image, registry, Dockerfile, Compose, Swarm, BuildKit, or OCI, it probably doesn't belong here.
What changed and why:
This project exists to deeply coupled with Docker ecosystem features rather than just being a standard application wrapped in a container. Here is how it directly relates to and leverages Docker:
Docker-in-Docker (DinD) & Workflow Isolation: The primary use case of this runner is to execute GitHub Actions workflows (which themselves often require running docker build or running test containers) entirely inside an isolated Docker container. It configures and optimizes the Docker socket binding safely.
Orchestration via Docker Compose: It utilizes docker-compose to allow DevOps engineers to horizontally scale their CI/CD infrastructure seamlessly (e.g., running docker-compose up --scale runner=5 to instantly spin up 5 parallel runners).
Multi-Platform Docker Architecture: The repository maintains specialized Dockerfile configurations and entrypoints to handle platform-specific nuances across Linux, Windows, and specifically macOS ARM64 (Apple Silicon) containers, which is a common pain point in containerized CI infrastructure.
Given that it provides a turnkey blueprint for orchestrating containerized CI/CD infrastructure via Docker, I believe it would be a highly relevant addition to the CI/CD section.
Best regards,
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/veggiemonk/awesome-docker/pull/1440
**Author:** [@youssefbrr](https://github.com/youssefbrr)
**Created:** 5/18/2026
**Status:** ✅ Merged
**Merged:** 7/2/2026
**Merged by:** [@veggiemonk](https://github.com/veggiemonk)
**Base:** `master` ← **Head:** `add-self-hosted-runner`
---
### 📝 Commits (3)
- [`971c9e3`](https://github.com/veggiemonk/awesome-docker/commit/971c9e3c9e63294ba031e303ae5a280f559b2e72) Add self-hosted-runner to CI/CD section
- [`a1bd47b`](https://github.com/veggiemonk/awesome-docker/commit/a1bd47b93cb21cd5daf312c33bdb24a098ad9f39) Merge branch 'master' into add-self-hosted-runner
- [`63f2f56`](https://github.com/veggiemonk/awesome-docker/commit/63f2f5634aadc7b04f53c8d97584eab42765ae1e) Remove By XXX on self hosted runner
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+1 -0)
</details>
### 📄 Description
# IF THE PROJECT JUST RUNS IN DOCKER, AUTOMATICALLY DENIED
- [x] I HAVE READ .github/CONTRIBUTING.md
Write the sentence: *"This project exists to ____."*
If the blank doesn't contain **Docker, container, image, registry, Dockerfile, Compose, Swarm, BuildKit, or OCI**, it probably doesn't belong here.
What changed and why:
This project exists to deeply coupled with Docker ecosystem features rather than just being a standard application wrapped in a container. Here is how it directly relates to and leverages Docker:
Docker-in-Docker (DinD) & Workflow Isolation: The primary use case of this runner is to execute GitHub Actions workflows (which themselves often require running docker build or running test containers) entirely inside an isolated Docker container. It configures and optimizes the Docker socket binding safely.
Orchestration via Docker Compose: It utilizes docker-compose to allow DevOps engineers to horizontally scale their CI/CD infrastructure seamlessly (e.g., running docker-compose up --scale runner=5 to instantly spin up 5 parallel runners).
Multi-Platform Docker Architecture: The repository maintains specialized Dockerfile configurations and entrypoints to handle platform-specific nuances across Linux, Windows, and specifically macOS ARM64 (Apple Silicon) containers, which is a common pain point in containerized CI infrastructure.
Given that it provides a turnkey blueprint for orchestrating containerized CI/CD infrastructure via Docker, I believe it would be a highly relevant addition to the CI/CD section.
Best regards,
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/veggiemonk/awesome-docker/pull/1440
Author: @youssefbrr
Created: 5/18/2026
Status: ✅ Merged
Merged: 7/2/2026
Merged by: @veggiemonk
Base:
master← Head:add-self-hosted-runner📝 Commits (3)
971c9e3Add self-hosted-runner to CI/CD sectiona1bd47bMerge branch 'master' into add-self-hosted-runner63f2f56Remove By XXX on self hosted runner📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
README.md(+1 -0)📄 Description
IF THE PROJECT JUST RUNS IN DOCKER, AUTOMATICALLY DENIED
Write the sentence: "This project exists to ____."
If the blank doesn't contain Docker, container, image, registry, Dockerfile, Compose, Swarm, BuildKit, or OCI, it probably doesn't belong here.
What changed and why:
This project exists to deeply coupled with Docker ecosystem features rather than just being a standard application wrapped in a container. Here is how it directly relates to and leverages Docker:
Docker-in-Docker (DinD) & Workflow Isolation: The primary use case of this runner is to execute GitHub Actions workflows (which themselves often require running docker build or running test containers) entirely inside an isolated Docker container. It configures and optimizes the Docker socket binding safely.
Orchestration via Docker Compose: It utilizes docker-compose to allow DevOps engineers to horizontally scale their CI/CD infrastructure seamlessly (e.g., running docker-compose up --scale runner=5 to instantly spin up 5 parallel runners).
Multi-Platform Docker Architecture: The repository maintains specialized Dockerfile configurations and entrypoints to handle platform-specific nuances across Linux, Windows, and specifically macOS ARM64 (Apple Silicon) containers, which is a common pain point in containerized CI infrastructure.
Given that it provides a turnkey blueprint for orchestrating containerized CI/CD infrastructure via Docker, I believe it would be a highly relevant addition to the CI/CD section.
Best regards,
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.