Optimize Dockerfiles and Compose files for secure, cache-friendly images.
npx skills add https://github.com/CloudyWing/ai-dotfiles --skill docker-cloudywing
Please help me install this Agent Skill. Skill: docker Source: https://github.com/CloudyWing/ai-dotfiles/tree/main/skills/docker Command: npx skills add https://github.com/CloudyWing/ai-dotfiles --skill docker-cloudywing
This Skill enforces Dockerfile and Docker Compose best practices to produce secure, small, and cache-efficient container images while avoiding common pitfalls like running as root, poor layer caching, missing health checks, and improper Compose syntax.
Create a multi-stage Dockerfile for a .NET web app that copies each project file then restores to preserve cache, uses matching sdk and runtime images, switches to a non-root user, includes a HEALTHCHECK, and produce a Compose v2 service with explicit versioned image tags.
High-intent search queries and answers about installing and using this skill.
Optimize Dockerfiles by applying multi-stage builds, matching runtime versions, enforcing non-root execution, and using a .dockerignore file to reduce build context. This approach produces smaller, secure, and cache-friendly container images.
To cache Docker layers effectively for .NET multi-project builds, copy project files individually before restoring dependencies to maximize cache hits. Place infrequently changed Dockerfile steps earlier to preserve the Docker layer cache.
Yes, Docker Compose Specification v2 compliance requires explicit versioned image tags for CI and production deployments. Using versioned tags ensures deployment readiness and prevents unexpected runtime environment changes.
Dockerfiles run as root by default if not explicitly configured. Fix this by switching to a non-root user in the final runtime stage to enforce runtime safety and meet deployment readiness requirements.
Add a HEALTHCHECK instruction to your Dockerfile and configure the corresponding health check parameters in your Docker Compose service. This ensures runtime safety and deployment readiness for your web services.
Yes, you can use Docker multi-stage builds for .NET web apps in CI pipelines by separating build and runtime stages. Use the sdk image for building and the aspnet or runtime image for the final stage while keeping versions aligned.
kierunbGenerate a Windows-based multi-stage Dockerfile for ASP.NET Framework applications.
ImaginerLabsGenerate GitHub Actions workflows, Dockerfiles, and Kubernetes manifests for Node.js applications.
olibartfastDeploy AutoMagicCalib microservice and web UI from NVIDIA NGC images using Docker Compose.
ArieGoldkinAutomate CI/CD pipelines, containerization, and Kubernetes deployments.
