docker-registry-deployment

Deploy container images to Docker registries using a six-phase lifecycle contract.

11|2|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/porcupine-md/jonggrang --skill docker-registry-deployment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docker-registry-deployment
Source: https://github.com/porcupine-md/jonggrang/tree/main/skills/library/deploy/docker-registry-deployment
Command: npx skills add https://github.com/porcupine-md/jonggrang --skill docker-registry-deployment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying container images to registries is error-prone and brittle without a standard lifecycle. This Skill enforces a six-phase Deployment Lifecycle Contract that standardizes authentication, build, provisioning, deploy, check, and rollback to improve reliability and repeatability.

Core Features & Use Cases

  • Six-phase deployment workflow (Authentication, Build, Install/Provisioning, Deploy, Checking, Update/Rollback) to ensure end-to-end reliability.
  • Registry compatibility across DockerHub, GHCR, AWS ECR, and Google Artifact Registry with explicit commands and guardrails.
  • Real-world scenarios include pushing images for production services, performing blue/green or canary updates, and rollback if checks fail.

Quick Start

Authenticate to your target registry and execute the six-phase deployment to push and verify your image.

Frequently Asked Questions about docker-registry-deployment

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

FAQPage Schema
How do I securely deploy Docker images to a registry?

Secure Docker image deployment requires a structured lifecycle enforcing authentication, build, provisioning, deployment, validation, and rollback phases to ensure reproducible and safe registry releases across platforms like DockerHub, GHCR, AWS ECR, and Google Artifact Registry.

What is the best way to standardize container image deployments across different registries?

Standardizing container image deployments involves applying a six-phase Deployment Lifecycle Contract with explicit commands and guardrails for authentication, build, and rollback, ensuring consistency across DockerHub, GHCR, AWS ECR, and Google Artifact Registry.

Does this deployment workflow support AWS ECR and Google Artifact Registry authentication?

Yes, the deployment workflow supports AWS ECR and Google Artifact Registry, providing explicit authentication commands and compatibility alongside DockerHub and GitHub Container Registry for secure image pushes.

How do I rollback a Docker deployment if validation checks fail?

To rollback a Docker deployment, follow the structured lifecycle's sixth phase which specifies practical commands and guardrails for reverting to a previous stable image when post-deployment validation checks fail.

When do I need a deployment lifecycle contract for container registries?

You need a deployment lifecycle contract when container image pushes become error-prone and brittle, requiring standardized authentication, build, provisioning, deploy, check, and rollback phases to improve release reliability and repeatability.

Can I perform blue/green or canary deployments using this registry workflow?

Yes, the registry workflow supports real-world scenarios including blue/green or canary updates, applying structured guardrails during the provisioning and deployment phases to ensure safe, reproducible releases.