Skip to content

jeremylongshore/tons-of-skills-marketplace / plugins/devops/container-registry-manager/skills/managing-container-registries

managing-container-registries

Verified

Execute use when you need to work with containerization. This skill provides container management and orchestration with comprehensive guidance and automation. Trigger with phrases like "containerize app", "manage containers", or "orchestrate deployment".

Managing Container Registries

Overview

Manage container registries across Docker Hub, AWS ECR, GCP Artifact Registry, Azure ACR, and self-hosted registries (Harbor, Nexus). Automate image tagging, lifecycle policies, cross-region replication, vulnerability scanning integration, and access control for container image storage and distribution.

Prerequisites

  • Docker CLI installed and authenticated to the target registry
  • Cloud provider CLI (aws, gcloud, az) for managed registries
  • Registry credentials configured (docker login or credential helpers)
  • Understanding of image naming conventions (registry/namespace/image:tag)
  • IAM permissions for registry operations (push, pull, delete, admin)

Instructions

  1. Identify the target registry type: ECR, Artifact Registry, ACR, Docker Hub, or self-hosted
  2. Configure authentication: set up credential helpers for automated access (docker-credential-ecr-login, gcloud auth configure-docker)
  3. Define image naming and tagging strategy: use semantic versioning for releases, git SHA for CI builds, latest only for development
  4. Create repository/namespace structure organized by team, application, or environment
  5. Configure lifecycle policies to auto-delete untagged images and images older than retention threshold (e.g., keep last 10 tagged images, delete untagged after 7 days)
  6. Set up vulnerability scanning: enable automatic scanning on push (ECR scan-on-push, GCP Container Analysis)
  7. Configure cross-region replication for disaster recovery and latency reduction
  8. Implement access control: read-only for CI pull, push access for CI build agents, admin for operators
  9. Generate Terraform/IaC for registry infrastructure and policies

Output

  • Terraform/CloudFormation for registry creation with lifecycle and replication policies
  • Docker credential helper configuration scripts
  • CI/CD pipeline steps for building, tagging, and pushing images
  • Lifecycle policy JSON (ECR) or cleanup scripts (Docker Hub, Harbor)
  • RBAC configurations for registry access control

Error Handling

ErrorCauseSolution
denied: requested access to the resource is deniedMissing push/pull permissions or expired tokenRe-authenticate with docker login or refresh credential helper; verify IAM policies
manifest unknown: manifest unknownImage tag does not exist in the registryVerify image name and tag; check if lifecycle policy deleted the image
no space left on device during pushRegistry storage quota exceededIncrease quota, run lifecycle cleanup, or delete unused images
unauthorized: authentication requiredCredential helper not configured or token expiredSet up credential helper (aws ecr get-login-password, gcloud auth configure-docker)
toomanyrequests: rate limit exceededDocker Hub pull rate limit hitUse authenticated pulls, mirror images to private registry, or upgrade Docker Hub plan

Examples

  • "Set up an AWS ECR repository with scan-on-push enabled, lifecycle policy to keep last 20 tagged images, and cross-region replication to us-west-2."
  • "Configure GCP Artifact Registry with Docker credential helper and a cleanup policy for images not pulled in 90 days."
  • "Create a CI pipeline step that builds a Docker image, tags it with the git SHA and latest, pushes to ECR, and fails if Critical vulnerabilities are found."

Resources

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall