AI SummaryAutomates configuration of container image registries (ghcr.io, Docker Hub, Harbor) with vulnerability scanning, image signing, and retention policies for secure CI/CD pipelines. Essential for DevOps engineers and platform teams managing containerized applications at scale.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "setup-container-registry" skill in my project. Please run this command in my terminal: # Install skill into the correct directory (2 files) mkdir -p .claude/skills/setup-container-registry && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/setup-container-registry/SKILL.md "https://raw.githubusercontent.com/pjt222/development-guides/main/skills/setup-container-registry/SKILL.md" && mkdir -p .claude/skills/setup-container-registry/references && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/setup-container-registry/references/EXAMPLES.md "https://raw.githubusercontent.com/pjt222/development-guides/main/skills/setup-container-registry/references/EXAMPLES.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Configure container image registries including GitHub Container Registry (ghcr.io), Docker Hub, and Harbor with automated image scanning, tagging strategies, retention policies, and CI/CD integration for secure image distribution. Use when setting up a private container registry, migrating from Docker Hub to self-hosted registries, implementing vulnerability scanning in CI/CD pipelines, managing multi-architecture images, enforcing image signing, or configuring automatic cleanup and retention policies.
Setup Container Registry
Configure production-ready container registries with security scanning, access control, and automated CI/CD integration.
When to Use
• Setting up private container registry for organization • Migrating from Docker Hub to self-hosted or alternative registries • Implementing image vulnerability scanning in CI/CD pipelines • Managing multi-architecture images (amd64, arm64) with manifests • Enforcing image signing and provenance verification • Configuring automatic image cleanup and retention policies
Inputs
• Required: Docker or Podman installed locally • Required: Registry credentials (personal access tokens, service accounts) • Optional: Self-hosted infrastructure for Harbor deployment • Optional: Kubernetes cluster for registry integration • Optional: Cosign/Notary for image signing • Optional: Trivy or Clair for vulnerability scanning
Procedure
> See Extended Examples for complete configuration files and templates.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster