docker-containerization

Generate Dockerfiles, docker-compose configurations, and deployment scripts for containerizing web applications.

2|1|Updated Jun 12, 2025
One-click install
npx skills add https://github.com/agent-trust-protocol/atp-core --skill docker-containerization-agent-trust-protocol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docker-containerization
Source: https://github.com/agent-trust-protocol/atp-core/tree/main/.claude/skills/docker-containerization
Command: npx skills add https://github.com/agent-trust-protocol/atp-core --skill docker-containerization-agent-trust-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Containerizing applications for development, production, and CI/CD requires writing optimized Dockerfiles, orchestration configs, and deployment scripts from scratch, which is error-prone and time-consuming. This Skill provides ready-to-use templates, management scripts, and deployment guides so you can containerize Next.js, React, and Node.js applications without deep Docker expertise. ## Core Features & Use Cases - Dockerfile Generation: Multi-stage production builds (~85% smaller images), development builds with hot reload, and Nginx static export variants. - Container Management Scripts: Bash scripts for building, running, pushing to registries (Docker Hub, ECR, GCR, ACR), and cleaning up Docker resources with dry-run support. - Orchestration & Deployment Guides: Reference documentation covering Docker Compose, Kubernetes, AWS ECS, Google Cloud Run, Azure Container Instances, and Digital Ocean App Platform. - Use Case: You need to deploy a Next.js app to production. Copy the production Dockerfile and .dockerignore, build with docker-build.sh, push to your registry with docker-push.sh, then follow the Kubernetes or ECS section of the orchestration guide to deploy. ## Quick Start Ask the AI to containerize your Next.js application for production and generate the Dockerfile, docker-compose setup, and build scripts.

Frequently Asked Questions about docker-containerization

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

FAQPage Schema
How do I containerize a Next.js app for production with Docker?▼

Copy the provided Dockerfile.production and .dockerignore to your project root, then build with docker-build.sh using the prod environment flag. The multi-stage build produces an Alpine-based image around 180MB with a non-root user and health checks.

How do I reduce Docker image size for Node.js applications?▼

Use multi-stage builds to separate build and runtime dependencies, choose an Alpine base image, and add a comprehensive .dockerignore file. These techniques typically reduce image size by 50-85% compared to a single-stage full Node image.

Can I deploy a Docker container to Kubernetes, ECS, or Cloud Run?▼

Yes, the container-orchestration reference includes deployment configurations and commands for Kubernetes, Amazon ECS, Google Cloud Run, Azure Container Instances, Digital Ocean App Platform, and Docker Compose, including auto-scaling and load balancing examples.

How do I push a Docker image to AWS ECR or Google GCR?▼

Use the docker-push.sh script with the registry flag, for example -r gcr.io/project-id or your ECR registry URL, plus the --repo flag for the repository name. It supports tagging and pushing multiple tags in one run.

Why does my Docker container exit immediately after starting?▼

Check the container logs with docker logs to see the error, verify the CMD or ENTRYPOINT is correct, and confirm there are no port conflicts. Running the container interactively with docker run -it helps diagnose startup failures.

Should I use Docker Compose or Kubernetes for my deployment?▼

Docker Compose suits local development and small single-host deployments with low complexity. Kubernetes fits large-scale deployments needing high availability, auto-scaling, and multi-cloud support, at the cost of higher operational complexity.