container-registries

Manage container registry operations including push/pull, authentication, lifecycle policies, and security controls.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/ToanPV90/dotfiles --skill container-registries-toanpv90
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: container-registries
Source: https://github.com/ToanPV90/dotfiles/tree/main/agents/.agents/skills/container-registries
Command: npx skills add https://github.com/ToanPV90/dotfiles --skill container-registries-toanpv90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Container teams need a reliable way to store, distribute, and govern container images across multiple registries (cloud and self-hosted) while keeping authentication, retention, and security practices consistent.

Core Features & Use Cases

  • Push/Pull Image Distribution: Tag, push, and pull images for Docker Hub, Amazon ECR, Azure ACR, Google GCR/Artifact Registry, GHCR, and self-hosted registries.
  • Registry Authentication & Access Control: Configure logins (CLI and credential-helper approaches) and handle cross-account or principal-based access policies.
  • Lifecycle, Retention, and Security: Implement lifecycle/retention policies to control storage growth and enable vulnerability scanning and image signing for supply-chain safety.
  • Image Lifecycle Management Example: Keep only the most recent N images in ECR to reduce storage cost while maintaining predictable rollback availability.

Quick Start

Use this skill to push an image to your registry by running the appropriate docker login for your platform and then tagging the image with the registry URL before pushing it.

Frequently Asked Questions about container-registries

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I push and pull container images across multiple cloud registries?

To manage container image distribution, you tag images with the registry URL, authenticate using platform-specific CLI logins, and then push or pull images across Docker Hub, ECR, ACR, or GCR.

How do I configure lifecycle policies to control registry storage costs?

Configuring lifecycle policies in container registries like ECR removes old or untagged images, keeping only the most recent N images to reduce storage costs while maintaining predictable rollback availability.

What is the best way to authenticate Docker to major cloud container registries?

The best way to authenticate Docker to cloud registries is using platform-specific CLI tools and credential helpers, which securely configure access for cross-account or principal-based image pull and push operations.

Does this approach support image scanning and signing for supply-chain security?

Yes, supply-chain security is supported by enabling vulnerability scanning and image signing workflows within the container registry, ensuring distributed images are validated and free from known security threats.

Do I need Docker or Podman to manage container registry operations?

Yes, you need Docker or Podman installed alongside relevant cloud CLI tooling for ECR, ACR, or GCR to execute the necessary commands for registry login, tagging, lifecycle configuration, and image distribution.

When should I implement cross-account access for a container registry?

You should implement cross-account access policies when distributing container images across different teams or cloud principals, ensuring secure authentication and controlled pull permissions for CI/CD pipelines.