Docker containerization fundamentals. Master container lifecycle, image management, networking, volumes, resource limits, and production deployment patterns. Use when building, running, debugging containers or implementing container orchestration.
Provides guidance for building, running, and debugging Docker containers with best practices.
npx claudepluginhub karchtho/my-claude-marketplaceThis skill is limited to using the following tools:
Comprehensive guide to containerization with Docker, from image fundamentals to production deployments.
# Build image
docker build -t myapp:latest .
# Run container (foreground)
docker run --rm -it myapp:latest
# Run container (background)
docker run -d --name my-container myapp:latest
# View logs
docker logs -f my-container
# Stop/start container
docker stop my-container
docker start my-container
# Remove container
docker rm my-container
# View processes
docker ps -a
# List images
docker images
# Tag image
docker tag myapp:latest myapp:v1.0.0
# Remove image
docker rmi myapp:latest
# Inspect image
docker inspect myapp:latest
# View image layers
docker history myapp:latest
# Use specific version tags (NOT latest)
FROM node:20.11-alpine
# Set working directory
WORKDIR /app
# Copy package files
COPY package*.json ./
# Install dependencies
RUN npm ci --only=production
# Copy application code
COPY . .
# Expose port (documentation only)
EXPOSE 3000
# Health check
HEALTHCHECK --interval=30s --timeout=5s --start-period=10s --retries=3 \
CMD node healthcheck.js
# Run application
CMD ["node", "server.js"]
# Build stage
FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci
COPY . .
RUN npm run build
# Production stage
FROM node:20-alpine
WORKDIR /app
COPY --from=builder /app/dist ./dist
COPY package*.json ./
RUN npm ci --only=production
EXPOSE 3000
CMD ["node", "dist/server.js"]
.dockerignore to exclude unnecessary files&&)latest)# List networks
docker network ls
# Create custom bridge network
docker network create myapp-net
# Run container on network
docker run -d --network myapp-net --name db postgres:15
docker run -d --network myapp-net --name api myapp:latest
# Container DNS resolution
# Services on same network can reach each other by container name
# Map single port
docker run -p 8080:3000 myapp:latest
# Map multiple ports
docker run -p 8080:3000 -p 8443:3000 myapp:latest
# Map to random port
docker run -p 3000 myapp:latest
# View port mappings
docker port my-container
# Create volume
docker volume create mydata
# Run container with volume
docker run -v mydata:/app/data myapp:latest
# View volume details
docker volume inspect mydata
# Clean up unused volumes
docker volume prune
# Mount host directory into container
docker run -v /host/path:/container/path myapp:latest
# Read-only mount
docker run -v /host/path:/container/path:ro myapp:latest
# Mount temporary filesystem (memory-backed)
docker run --tmpfs /tmp:rw,size=1gb myapp:latest
# Limit memory
docker run -m 512m myapp:latest
# Limit CPU (1.0 = 1 core, 0.5 = half core)
docker run --cpus 1.0 myapp:latest
# Memory swap limit
docker run -m 512m --memory-swap 1g myapp:latest
# CPU shares (relative priority)
docker run --cpu-shares 1024 myapp:latest
# Monitor container resources
docker stats
# Specific container
docker stats my-container
# Execute command in running container
docker exec -it my-container /bin/sh
# Run one-off command
docker exec my-container npm test
# View detailed container info
docker inspect my-container
# View environment variables
docker inspect my-container | grep -A 20 "Env"
# View mounted volumes
docker inspect my-container | grep -A 10 "Mounts"
# Tail logs
docker logs -f my-container
# Last 100 lines
docker logs --tail 100 my-container
# With timestamps
docker logs -t my-container
# Since specific time
docker logs --since 2025-01-15T10:00:00 my-container
# Create non-root user
RUN groupadd -r appuser && useradd -r -g appuser appuser
# Use non-root user
USER appuser
docker run --read-only -v /tmp:/tmp myapp:latest
# Drop unnecessary capabilities
docker run --cap-drop=ALL --cap-add=NET_BIND_SERVICE myapp:latest
# Scan image for vulnerabilities
docker scan myapp:latest
# Build with BuildKit (enables better layer caching and features)
DOCKER_BUILDKIT=1 docker build .
# Login
docker login
# Tag for registry
docker tag myapp:latest username/myapp:latest
# Push image
docker push username/myapp:latest
# Pull image
docker pull username/myapp:latest
# Logout
docker logout
# Login to private registry
docker login registry.example.com
# Tag for private registry
docker tag myapp:latest registry.example.com/myapp:latest
# Push to private registry
docker push registry.example.com/myapp:latest
# Check exit code and error logs
docker logs my-container
# View container events
docker events --filter "container=my-container"
# Inspect container config
docker inspect my-container | grep -A 20 "State"
# Monitor in real-time
docker stats
# Identify processes consuming resources
docker top my-container
# Test DNS resolution
docker exec my-container nslookup db
# Test connectivity
docker exec my-container curl http://db:5432
# View network settings
docker network inspect myapp-net
HEALTHCHECK --interval=30s --timeout=5s --start-period=10s --retries=3 \
CMD curl -f http://localhost:3000/health || exit 1
# Applications should handle SIGTERM gracefully
# Docker gives 10 seconds (default) before SIGKILL
docker stop --time 30 my-container
# Wait for container to stop (with timeout)
docker stop -t 30 my-container
# Verify container stopped
docker wait my-container
echo $? # Exit code
docker run -it \
-v $(pwd):/app \
-p 3000:3000 \
-e NODE_ENV=development \
myapp:dev
docker run -d \
--name myapp \
--restart unless-stopped \
-m 1g \
--cpus 2 \
-p 3000:3000 \
-e NODE_ENV=production \
--health-cmd="curl -f http://localhost:3000/health" \
--health-interval=30s \
myapp:latest
# Main application
docker run -d --name app myapp:latest
# Sidecar (logging, monitoring, etc)
docker run -d --network container:app --volumes-from app logging-agent:latest
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Search, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.