docker-push

Push container images to DockerHub, ghcr.io, or AWS ECR with authentication and tagging.

1|1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/dennisonbertram/go-agent-harness --skill docker-push
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docker-push
Source: https://github.com/dennisonbertram/go-agent-harness/tree/main/skills/docker-push
Command: npx skills add https://github.com/dennisonbertram/go-agent-harness --skill docker-push

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Push container images to registries efficiently by centralizing authentication, tagging, and push workflows across DockerHub, ghcr.io, and AWS ECR.

Core Features & Use Cases

  • Authenticate with registries (DockerHub, ghcr.io, ECR)
  • Tag images for different registries and versions
  • Push to multiple registries and handle multi-platform builds

Quick Start

Authenticate with your registry, tag the image, and push it to the registry to complete a push cycle.

Frequently Asked Questions about docker-push

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

FAQPage Schema
How do I push Docker images to multiple registries like DockerHub, ghcr.io, and AWS ECR?

Pushing Docker images to multiple registries requires authenticating with each target, applying registry-specific tagging conventions, and executing push commands. This workflow centralizes publishing across DockerHub, ghcr.io, and AWS ECR for CI pipelines and manual deployments.

What's the best way to handle Docker authentication for CI/CD workflows?

Handling Docker authentication for CI/CD workflows involves using login prompts and registry credentials to authenticate before tagging and pushing images. This centralizes access across DockerHub, ghcr.io, and AWS ECR for automated deployment pipelines.

Does this approach support multi-platform Docker builds and registry pushes?

Yes, this approach supports multi-platform Docker builds and pushes. It handles registry-specific nuances for multi-platform builds while applying authentication and tagging guidelines to publish images across DockerHub, ghcr.io, and AWS ECR.

How do I tag Docker images for different registries and versions?

Tagging Docker images for different registries and versions requires applying registry-specific naming conventions before pushing. This ensures images are correctly identified for DockerHub, ghcr.io, or AWS ECR across development pipelines and manual deployments.

Can I use this for both automated CI workflows and manual Docker deployments?

Yes, you can use this for both automated CI workflows and manual Docker deployments. The push workflow applies authentication, tagging guidelines, and push commands suitable for development pipelines and manual image publishing to DockerHub, ghcr.io, and AWS ECR.

Why does pushing Docker images to AWS ECR fail in my deployment pipeline?

Pushing Docker images to AWS ECR may fail due to registry-specific authentication nuances. Ensure you complete the registry login process and apply correct tagging conventions before executing push commands in your CI workflows or manual deployments.