setup-container-registrylisted

# 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](references/EXAMPLES.md) for complete configuration files and templates. ### Step 1: Configure GitHub Container Registry (ghcr.io) Set up GitHub Container Registry with personal access tokens and CI/CD integration. ```bash # Create GitHub Personal Access Token # Go to: Settings → Developer settings → Personal access tokens → Tokens (classic) # Required scopes: write:packages, read:packages, delete:packages # Login to ghcr.io echo $GITHUB_TOKEN | docker login ghcr.io -u USERNAME --password-stdin # Verify login docker info | grep -A 5 "Reg