docker-registry-deployment

Stars10

Forks2

UpdatedMay 24, 2026 at 09:39

Deep knowledge about building and pushing container images to Docker registries (DockerHub, GHCR, ECR, GCR).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

porcupine-md

porcupine-md/jonggrang

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	docker-registry-deployment
description	Deep knowledge about building and pushing container images to Docker registries (DockerHub, GHCR, ECR, GCR).
type	transform
tier	library
domain	deploy
trigger	when deploying to a Docker Registry

Context

Deploying {{project_name}} ({{project_type}}) to a Docker Registry (DockerHub, GitHub Container Registry, AWS ECR, Google Artifact Registry). You will follow a strict 6-phase Deployment Lifecycle Contract.

Instructions

Execute the following phases in order:

Phase 1: Authentication

Authenticate to the target container registry.
For DockerHub or GHCR, use docker login <registry-url> -u <username> -p <password/token>. (For GHCR, the URL is ghcr.io).
For AWS ECR, run aws ecr get-login-password --region <region> | docker login --username AWS --password-stdin <account-id>.dkr.ecr.<region>.amazonaws.com.
For GCP GCR/Artifact Registry, run gcloud auth configure-docker <region>-docker.pkg.dev.

Phase 2: Build

Prepare the artifacts for deployment.
Build your Docker image: docker build -t <registry-url>/<repository-name>/<image-name>:<tag> .
Consider using --build-arg if your Dockerfile requires environment variables during the build process.
(Optional but recommended) Build multi-architecture images using docker buildx build --platform linux/amd64,linux/arm64 -t <registry-url>/<repository-name>/<image-name>:<tag> --push .

Phase 3: Install / Provisioning

Ensure the target repository exists in the registry.
For AWS ECR, you might need to create the repository first: aws ecr create-repository --repository-name <repository-name>.
For DockerHub or GHCR, pushing to a new repository name usually creates it automatically (if permissions allow).

Phase 4: Deploy

Ship the artifact to the registry.
Push the image: docker push <registry-url>/<repository-name>/<image-name>:<tag>.
If you used docker buildx build --push in Phase 2, this step is already completed.
Optionally, tag the same image as latest and push it as well: docker tag <registry-url>/<repository-name>/<image-name>:<tag> <registry-url>/<repository-name>/<image-name>:latest && docker push <registry-url>/<repository-name>/<image-name>:latest.

Phase 5: Checking

Verify the deployment was successful.
The docker push command output should confirm all layers were pushed.
You can also verify by pulling the image: docker pull <registry-url>/<repository-name>/<image-name>:<tag>.
For ECR, you can list images: aws ecr describe-images --repository-name <repository-name>.

Phase 6: Update / Rollback

If Phase 5 fails (e.g., authentication error or network timeout), check your credentials and network connection.
If a bad image was pushed, there is no direct "rollback" in a registry, but you should delete the bad tag or push the previous known-good image to the latest tag.
Note the failure in the progress log.

Validation

Registry authentication (docker login) succeeds.
Docker image builds successfully.
Docker image is pushed to the registry.
Image can be pulled successfully.

More from this repository

same repository

jonggrang

porcupine-md/jonggrang

Deterministic AI development workflow orchestrator. Manages task boards (.jonggrang/jonggrang-tasks.json), runs 16-phase pipelines (BUGFIX/SMALL/MEDIUM/LARGE), installs lifecycle hooks for Claude Code and OpenCode, and coordinates five specialist roles (Lead/Developer/Reviewer/TestLead/Tester). Use when planning features, executing multi-step development workflows, or orchestrating AI coding agents. Run via npx jonggrang.

2026-07-2910

orchestrating-feature

porcupine-md/jonggrang

16-phase feature orchestration workflow. Runs in the main thread as Kernel Mode. Coordinates the Lead→Developer→Reviewer→TestLead→Tester assembly line.

2026-06-2310

persisting-agent-outputs

porcupine-md/jonggrang

Protocol for agents to write structured outputs that survive session resets and are findable by the orchestrator.

2026-06-1310

porcupine-md/jonggrang

GitHub workflow automation with the gh CLI — pull requests, issues, releases, the REST/GraphQL API, and safe message escaping. Auth via GH_TOKEN (set in global settings, attached to the sandbox env).

2026-06-0810

glab

porcupine-md/jonggrang

GitLab workflow automation with the glab CLI — merge requests, issues, CI, releases, and safe message escaping. Auth via GITLAB_TOKEN (set in global settings, attached to the sandbox env).

2026-06-0810

iterating-to-completion

porcupine-md/jonggrang

Prevents premature exit and infinite loops. Three mechanisms: Completion Promises, Scratchpads, Loop Detection.

2026-05-2410

name	docker-registry-deployment
description	Deep knowledge about building and pushing container images to Docker registries (DockerHub, GHCR, ECR, GCR).
type	transform
tier	library
domain	deploy
trigger	when deploying to a Docker Registry

Context

Instructions

Execute the following phases in order:

Phase 1: Authentication

Authenticate to the target container registry.
For DockerHub or GHCR, use docker login <registry-url> -u <username> -p <password/token>. (For GHCR, the URL is ghcr.io).
For AWS ECR, run aws ecr get-login-password --region <region> | docker login --username AWS --password-stdin <account-id>.dkr.ecr.<region>.amazonaws.com.
For GCP GCR/Artifact Registry, run gcloud auth configure-docker <region>-docker.pkg.dev.

Phase 2: Build

Prepare the artifacts for deployment.
Build your Docker image: docker build -t <registry-url>/<repository-name>/<image-name>:<tag> .
Consider using --build-arg if your Dockerfile requires environment variables during the build process.
(Optional but recommended) Build multi-architecture images using docker buildx build --platform linux/amd64,linux/arm64 -t <registry-url>/<repository-name>/<image-name>:<tag> --push .

Phase 3: Install / Provisioning

Ensure the target repository exists in the registry.
For AWS ECR, you might need to create the repository first: aws ecr create-repository --repository-name <repository-name>.
For DockerHub or GHCR, pushing to a new repository name usually creates it automatically (if permissions allow).

Phase 4: Deploy

Ship the artifact to the registry.
Push the image: docker push <registry-url>/<repository-name>/<image-name>:<tag>.
If you used docker buildx build --push in Phase 2, this step is already completed.
Optionally, tag the same image as latest and push it as well: docker tag <registry-url>/<repository-name>/<image-name>:<tag> <registry-url>/<repository-name>/<image-name>:latest && docker push <registry-url>/<repository-name>/<image-name>:latest.

Phase 5: Checking

Verify the deployment was successful.
The docker push command output should confirm all layers were pushed.
You can also verify by pulling the image: docker pull <registry-url>/<repository-name>/<image-name>:<tag>.
For ECR, you can list images: aws ecr describe-images --repository-name <repository-name>.

Phase 6: Update / Rollback

If Phase 5 fails (e.g., authentication error or network timeout), check your credentials and network connection.
If a bad image was pushed, there is no direct "rollback" in a registry, but you should delete the bad tag or push the previous known-good image to the latest tag.
Note the failure in the progress log.

Validation

Registry authentication (docker login) succeeds.
Docker image builds successfully.
Docker image is pushed to the registry.
Image can be pulled successfully.