How do I install the Docker Cicd Patterns skill?

Run npx skillmds add majiayu000/docker-cicd-patterns in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Docker Cicd Patterns safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Docker Cicd Patterns?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Docker Cicd Patterns free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Docker Cicd Patterns?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Docker Cicd Patterns by majiayu000 — Agent Skill

Name: Docker Cicd Patterns
Rating: 4.5 (4 reviews)
Author: majiayu000

Docker Cicd Patterns

Use this skill when creating or modifying Dockerfiles, docker-compose files, GitHub Actions workflows, or deployment pipelines. Triggers on: container builds, CI/CD configuration, deployment automation, Azure Container App Jobs, Docker Hub, or any mention of "Docker", "container", "GitHub Actions", "workflow", "CI/CD", "pipeline", "deploy", or "build".

majiayu000 b0fb5b4 2 files · 2.8 KB Updated Sep 9, 2026 567 repo stars

File contents

Docker & CI/CD Patterns — DoclingOptimisation

Dockerfile Standards

Multi-stage build: builder (compile deps, pre-fetch models) + runtime (slim, non-root)
Base image: python:3.14-slim-bookworm (pinned, not :latest)
Non-root user: docling:docling
uv for package management — uv sync --frozen --no-dev
Models pre-fetched at build time (no network at runtime)
CPU-only PyTorch from https://download.pytorch.org/whl/cpu
.dockerignore excludes .git, .claude, .history, .firecrawl, logs, research docs

Docker Compose (Local Dev)

Compose-native limits (mem_limit, cpus) for Docker Desktop
Volume mounts: ./input:/home/docling/input:ro, ./output:/home/docling/output
Default threads: DOCLING_NUM_THREADS=10 for local benchmarking

Azure Container App Job

This is a batch/one-shot workload — use Container App Jobs, NOT revision-based apps
CPU profile: 4 vCPUs / 8 Gi, set DOCLING_NUM_THREADS=4
GPU profile: NC8as-T4 / 8 vCPUs / 56 Gi, requires CUDA PyTorch build, set DOCLING_DEVICE=cuda
Container registry: Docker Hub (migration to ACR planned)

GitHub Actions

Separate CI (lint, format-check, type-check) from CD (build, push to Docker Hub)
Use astral-sh/setup-uv@v4 for uv in CI
Use --frozen for reproducible installs
Pin action versions
Use concurrency groups to cancel redundant runs
For Docker Hub: use docker/login-action@v3 + docker/build-push-action@v6

Image Tagging

latest for main branch
sha-<short-sha> for every push
Semantic version tags for releases

---name: docker-cicd-patternsdescription: Use this skill when creating or modifying Dockerfiles, docker-compose files, GitHub Actions workflows, or deployment pipelines. Triggers on: container builds, CI/CD configuration, deployment automation, Azure Container App Jobs, Docker Hub, or any mention of "Docker", "container", "GitHub Actions", "workflow", "CI/CD", "pipeline", "deploy", or "build".--- # Docker & CI/CD Patterns — DoclingOptimisation ## Dockerfile Standards - Multi-stage build: builder (compile deps, pre-fetch models) + runtime (slim, non-root) - Base image: `python:3.14-slim-bookworm` (pinned, not `:latest`) - Non-root user: `docling:docling` - uv for package management — `uv sync --frozen --no-dev` - Models pre-fetched at build time (no network at runtime) - CPU-only PyTorch from `https://download.pytorch.org/whl/cpu` - `.dockerignore` excludes .git, .claude, .history, .firecrawl, logs, research docs ## Docker Compose (Local Dev) - Compose-native limits (`mem_limit`, `cpus`) for Docker Desktop - Volume mounts: `./input:/home/docling/input:ro`, `./output:/home/docling/output` - Default threads: `DOCLING_NUM_THREADS=10` for local benchmarking ## Azure Container App Job - This is a **batch/one-shot workload** — use Container App Jobs, NOT revision-based apps - CPU profile: 4 vCPUs / 8 Gi, set `DOCLING_NUM_THREADS=4` - GPU profile: NC8as-T4 / 8 vCPUs / 56 Gi, requires CUDA PyTorch build, set `DOCLING_DEVICE=cuda` - Container registry: Docker Hub (migration to ACR planned) ## GitHub Actions - Separate CI (lint, format-check, type-check) from CD (build, push to Docker Hub) - Use `astral-sh/setup-uv@v4` for uv in CI - Use `--frozen` for reproducible installs - Pin action versions - Use concurrency groups to cancel redundant runs - For Docker Hub: use `docker/login-action@v3` + `docker/build-push-action@v6` ## Image Tagging - `latest` for main branch - `sha-<short-sha>` for every push - Semantic version tags for releases

Frequently asked questions