Prompt file imported from rhixecompany/sandbox (.github/prompts/ci-cd/all-repo-docker-setup/all-repo-docker-setup.prompt.md). Copyright stays with the author.

Goal

Iterate over a list of rhixecompany repositories, generate or repair Dockerfiles, build images, run security scans, and clean up unused Docker resources with a tracked plan.

Context

Phases

Bulk Docker Setup Across Repositories

Name: all-repo-docker-setup
Author: rhixecompany

Iterate over every rhixecompany repository, generate or repair Dockerfiles, build images, security-scan them, and clean up unused Docker resources.

Systematically process all repositories under rhixecompany to ensure each has a valid Dockerfile or docker-compose.yml, builds successfully, passes security scanning, and has a documented cleanup plan. Unused Docker resources are reclaimed with a tracked report.

Prerequisites

gh CLI authenticated and able to list rhixecompany repos
Docker daemon running and accessible
trivy installed for security scanning
docker CLI with docker compose plugin
Write access to ~/Desktop/SandBox/projects/

Inputs

The list of repositories from gh repo list rhixecompany --limit 100 --json name,url
Existing Docker artifacts in each repo (Dockerfile, docker-compose.yml)
Docker images built during the process

Outputs

A valid Dockerfile or docker-compose.yml in each repository (created or repaired)
All images built successfully
Security scan report per repository (Trivy output)
A cleanup report listing freed disk space

Steps

1. List repositories

List all rhixecompany repositories:

gh repo list rhixecompany --limit 100 --json name,url

Clone each repository to ~/Desktop/SandBox/projects/:

git clone <repository_url> ./projects/<repository_name>

2. Generate or repair Docker configuration

For each repository:

Check for existing Dockerfile or docker-compose.yml
If no Docker configuration exists, generate one based on the project's language (Node.js, Python, Go, Rust, etc.)
If a Dockerfile exists but is broken, debug, fix, and update it to a smaller base image
Build the image to verify it works:
```
docker build -t <image_name> .
```
If only docker-compose.yml exists, build with:
```
docker-compose build
```

3. Security scan

Run Trivy scan on each built image:

trivy image --severity HIGH,CRITICAL <image_name>

Record findings and fix critical vulnerabilities by updating base images or dependencies.

4. Cleanup

Remove unused containers:
```
docker container prune -f
```
Remove unused images:
```
docker image prune -a -f
```
Remove unused volumes:
```
docker volume prune -f
```
Remove build caches:
```
docker buildx builder prune -f
```
Report freed space:
```
docker system df
```

Rules

Scope discipline — Only operate on rhixecompany repositories
Minimal changes — Fix the smallest issue needed to build successfully
Track everything — Log results to docker_setup.log in each repo root
No Docker config found — Log "No Docker configuration found for this repository" to docker_setup.log if neither file exists

Verification

Each repository has either a Dockerfile or docker-compose.yml
All images build without errors
No HIGH/CRITICAL vulnerabilities remain (or documented rationale for exceptions)
Cleanup report is saved

Out of Scope

Workflow

Modifying application code beyond Docker-related config
Production deployment orchestration

## Table of Contents ## Goal Iterate over a list of rhixecompany repositories, generate or repair Dockerfiles, build images, run security scans, and clean up unused Docker resources with a tracked plan. ## Context ## Phases # Bulk Docker Setup Across Repositories > Iterate over every rhixecompany repository, generate or repair Dockerfiles, build images, security-scan them, and clean up unused Docker resources. Systematically process all repositories under `rhixecompany` to ensure each has a valid Dockerfile or `docker-compose.yml`, builds successfully, passes security scanning, and has a documented cleanup plan. Unused Docker resources are reclaimed with a tracked report. ## Prerequisites - `gh` CLI authenticated and able to list `rhixecompany` repos - Docker daemon running and accessible - `trivy` installed for security scanning - `docker` CLI with `docker compose` plugin - Write access to `~/Desktop/SandBox/projects/` ## Inputs - The list of repositories from `gh repo list rhixecompany --limit 100 --json name,url` - Existing Docker artifacts in each repo (Dockerfile, docker-compose.yml) - Docker images built during the process ## Outputs - A valid Dockerfile or `docker-compose.yml` in each repository (created or repaired) - All images built successfully - Security scan report per repository (Trivy output) - A cleanup report listing freed disk space ## Steps ### 1. List repositories 1. List all rhixecompany repositories: ```bash gh repo list rhixecompany --limit 100 --json name,url ``` 2. Clone each repository to `~/Desktop/SandBox/projects/`: ```bash git clone <repository_url> ./projects/<repository_name> ``` ### 2. Generate or repair Docker configuration For each repository: 1. Check for existing `Dockerfile` or `docker-compose.yml` 2. If no Docker configuration exists, generate one based on the project's language (Node.js, Python, Go, Rust, etc.) 3. If a Dockerfile exists but is broken, debug, fix, and update it to a smaller base image 4. Build the image to verify it works: ```bash docker build -t <image_name> . ``` 5. If only `docker-compose.yml` exists, build with: ```bash docker-compose build ``` ### 3. Security scan Run Trivy scan on each built image: ```bash trivy image --severity HIGH,CRITICAL <image_name> ``` Record findings and fix critical vulnerabilities by updating base images or dependencies. ### 4. Cleanup 1. Remove unused containers: ```bash docker container prune -f ``` 2. Remove unused images: ```bash docker image prune -a -f ``` 3. Remove unused volumes: ```bash docker volume prune -f ``` 4. Remove build caches: ```bash docker buildx builder prune -f ``` 5. Report freed space: ```bash docker system df ``` ## Rules - **Scope discipline** — Only operate on rhixecompany repositories - **Minimal changes** — Fix the smallest issue needed to build successfully - **Track everything** — Log results to `docker_setup.log` in each repo root - **No Docker config found** — Log "No Docker configuration found for this repository" to `docker_setup.log` if neither file exists ## Verification - Each repository has either a `Dockerfile` or `docker-compose.yml` - All images build without errors - No HIGH/CRITICAL vulnerabilities remain (or documented rationale for exceptions) - Cleanup report is saved ## Out of Scope ## Workflow <content> - Modifying application code beyond Docker-related config - Production deployment orchestration

{ "prompt": "## Table of Contents\n\n## Goal\nIterate over a list of rhixecompany repositories, generate or repair Dockerfiles, build images, run security scans, and clean up unused Docker resources with a tracked plan.\n\n## Context\n\n## Phases\n\n\n# Bulk Docker Setup Across Repositories\n\n> Iterate over every rhixecompany repository, generate or repair Dockerfiles, build images, security-scan them, and clean up unused Docker resources.\n\n\nSystematically process all repositories under `rhixecompany` to ensure each has a valid Dockerfile or `docker-compose.yml`, builds successfully, passes security scanning, and has a documented cleanup plan. Unused Docker resources are reclaimed with a tracked report.\n\n## Prerequisites\n\n- `gh` CLI authenticated and able to list `rhixecompany` repos\n- Docker daemon running and accessible\n- `trivy` installed for security scanning\n- `docker` CLI with `docker compose` plugin\n- Write access to `~/Desktop/SandBox/projects/`\n\n## Inputs\n\n- The list of repositories from `gh repo list rhixecompany --limit 100 --json name,url`\n- Existing Docker artifacts in each repo (Dockerfile, docker-compose.yml)\n- Docker images built during the process\n\n## Outputs\n\n- A valid Dockerfile or `docker-compose.yml` in each repository (created or repaired)\n- All images built successfully\n- Security scan report per repository (Trivy output)\n- A cleanup report listing freed disk space\n\n## Steps\n\n### 1. List repositories\n\n1. List all rhixecompany repositories:\n ```bash\n gh repo list rhixecompany --limit 100 --json name,url\n ```\n2. Clone each repository to `~/Desktop/SandBox/projects/`:\n ```bash\n git clone <repository_url> ./projects/<repository_name>\n ```\n\n### 2. Generate or repair Docker configuration\n\nFor each repository:\n1. Check for existing `Dockerfile` or `docker-compose.yml`\n2. If no Docker configuration exists, generate one based on the project's language (Node.js, Python, Go, Rust, etc.)\n3. If a Dockerfile exists but is broken, debug, fix, and update it to a smaller base image\n4. Build the image to verify it works:\n ```bash\n docker build -t <image_name> .\n ```\n5. If only `docker-compose.yml` exists, build with:\n ```bash\n docker-compose build\n ```\n\n### 3. Security scan\n\nRun Trivy scan on each built image:\n```bash\ntrivy image --severity HIGH,CRITICAL <image_name>\n```\n\nRecord findings and fix critical vulnerabilities by updating base images or dependencies.\n\n### 4. Cleanup\n\n1. Remove unused containers:\n ```bash\n docker container prune -f\n ```\n2. Remove unused images:\n ```bash\n docker image prune -a -f\n ```\n3. Remove unused volumes:\n ```bash\n docker volume prune -f\n ```\n4. Remove build caches:\n ```bash\n docker buildx builder prune -f\n ```\n5. Report freed space:\n ```bash\n docker system df\n ```\n\n## Rules\n\n- **Scope discipline** — Only operate on rhixecompany repositories\n- **Minimal changes** — Fix the smallest issue needed to build successfully\n- **Track everything** — Log results to `docker_setup.log` in each repo root\n- **No Docker config found** — Log \"No Docker configuration found for this repository\" to `docker_setup.log` if neither file exists\n\n## Verification\n\n- Each repository has either a `Dockerfile` or `docker-compose.yml`\n- All images build without errors\n- No HIGH/CRITICAL vulnerabilities remain (or documented rationale for exceptions)\n- Cleanup report is saved\n\n## Out of Scope\n\n## Workflow\n\n<content>\n\n- Modifying application code beyond Docker-related config\n- Production deployment orchestration", "variables": [], "notes": "Iterate over a list of rhixecompany repositories, generate or repair Dockerfiles, build images, run security scans, and clean up unused Docker resources with a tracked plan.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/rhixecompany/sandbox", "path": ".github/prompts/ci-cd/all-repo-docker-setup/all-repo-docker-setup.prompt.md", "ref": "a392d514ee6d8ff4ec01e32492d3aa7cc4601199", "url": "https://github.com/rhixecompany/sandbox/blob/a392d514ee6d8ff4ec01e32492d3aa7cc4601199/.github/prompts/ci-cd/all-repo-docker-setup/all-repo-docker-setup.prompt.md", "key": "rhixecompany/sandbox/.github/prompts/ci-cd/all-repo-docker-setup/all-repo-docker-setup.prompt.md" } } }

all-repo-docker-setup

About

Table of Contents