[PR #1440] Add self-hosted-runner to CI/CD section #26389

New Issue

GiteaMirror · 2026-06-16T04:22:52-05:00

GiteaMirror commented

2026-06-16 04:22:52 -05:00

📋 Pull Request Information

Original PR: https://github.com/veggiemonk/awesome-docker/pull/1440
Author: @youssefbrr
Created: 5/18/2026
Status: 🔄 Open

Base: master ← Head: add-self-hosted-runner

📝 Commits (3)

f3562ff Add self-hosted-runner to CI/CD section
665cb06 Merge branch 'master' into add-self-hosted-runner
a7e43d7 Merge branch 'master' into add-self-hosted-runner

📊 Changes

1 file changed (+5 additions, -0 deletions)

View changed files

📝 README.md (+5 -0)

📄 Description

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:** 🔄 Open **Base:** `master` ← **Head:** `add-self-hosted-runner` --- ### 📝 Commits (3) - [`f3562ff`](https://github.com/veggiemonk/awesome-docker/commit/f3562ff4e3c4f963db94ad4e59073b1d07f19448) Add self-hosted-runner to CI/CD section - [`665cb06`](https://github.com/veggiemonk/awesome-docker/commit/665cb06a9d9e685604eb866cc870c8009a6d31d6) Merge branch 'master' into add-self-hosted-runner - [`a7e43d7`](https://github.com/veggiemonk/awesome-docker/commit/a7e43d754f614328c35ac35105c2f6c0c45a522e) Merge branch 'master' into add-self-hosted-runner ### 📊 Changes **1 file changed** (+5 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+5 -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>

GiteaMirror added the pull-request label 2026-06-16 04:22:52 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-docker#26389