Optimize Docker Containerization and Deployment

Docker Expert provides a workflow for analyzing, improving, and reviewing Docker container setups. It begins with environment and project inspection, identifies the problem category, applies a relevant solution, and validates the result. Guidance covers Dockerfile structure, layer caching, multi-stage builds, build context, base image selection, security hardening, runtime behavior, networking, and development workflows.

Optimization techniques include separating dependency installation from source copying, reducing unnecessary files with .dockerignore, choosing a suitable base image, and keeping production stages limited to required artifacts. Security topics include running as a non-root user, avoiding secrets in image layers or environment variables, keeping base images updated, limiting capabilities and resources, and scanning for vulnerabilities. Compose and orchestration review covers health checks, service dependencies, network isolation, persistent volumes, restart policies, and environment-specific configuration.

Further production checks cover CPU and memory limits, restart policies, multi-architecture builds with docker buildx, package-manager cache mounts with BuildKit, build-time secrets, and custom health-check scripts. For Compose, inspect health-gated service dependencies, internal backend networks, persistent volumes, and separate development targets with hot-reload mounts. The review checklist also checks that tests stay isolated from production images, only necessary ports are exposed, and build artifacts and package caches are excluded from the final image.

Diagnostics map symptoms to likely causes: cache invalidation and large build contexts slow builds; build tools and unnecessary files inflate images; outdated bases, embedded secrets, or root execution trigger security findings; missing networks or conflicting ports break service discovery; and volume or environment mismatches break hot reload. Resolve each with the corresponding cache, image, security, network, or development configuration. Handoff guidance routes Kubernetes pod/service/ingress work, CI/CD automation, complex database persistence, application-code performance, and Terraform or cloud deployment to the specialist owning that layer.

Use this skill when working on Dockerfiles, container build performance, image size, runtime security, Compose configuration, or container diagnostics. It can support reviews of build and production readiness and help establish repeatable container standards.

The source directs highly specialized Kubernetes orchestration, container CI/CD, cloud-specific container deployment, and complex database persistence questions to more focused expertise. It also cautions that container validation should be performed in the target environment rather than assumed from a configuration review alone.

Inputs can include Dockerfiles, Compose files, .dockerignore, build output, image history, container status, network and volume configuration, and observed symptoms. The process can produce an optimized Dockerfile, a hardened runtime configuration, a troubleshooting plan, or a checklist of required changes. Validate builds, inspect image history, review security, start and inspect runtime containers, check shutdown behavior, and validate Compose configuration.

The environment check includes this command:

docker --version 2>/dev/null

The guide references Docker, Docker Compose, Docker Scout, Swarm, multi-stage build workflows, and health checks. It includes handoff guidance for Kubernetes, GitHub Actions, database, application-language, and infrastructure automation concerns.

Developers, DevOps engineers, and maintainers can use this skill to make container builds more efficient, images smaller, and runtime configuration safer. It is also suited to teams establishing container review standards for development and production.