docker

Applies containerization best practices to Dockerfiles, Compose files, and runtime configuration.

1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/Fidasek009/agents --skill docker-fidasek009
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docker
Source: https://github.com/Fidasek009/agents/tree/main/.kilo/skills/docker
Command: npx skills add https://github.com/Fidasek009/agents --skill docker-fidasek009

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often ship Docker images and Compose files with unpinned versions, bloated layers, embedded secrets, and root-run containers, leading to unreproducible builds and security risks. This Skill provides a concrete standards checklist for writing and reviewing container configurations. ## Core Features & Use Cases - Dockerfile Standards: Enforces pinned base images, multi-stage builds, build-cache-friendly layer ordering, non-root users, and exec-form CMD/ENTRYPOINT. - Runtime & Secrets Guidance: Externalizes configuration via environment variables and keeps secrets out of images and committed files. - Compose File Rules: Covers pinned service images, named volumes, secrets handling, and separation of local-only overrides. - Use Case: Before merging a pull request that adds a new service, use this Skill to review the Dockerfile and docker-compose.yml against production containerization standards. ## Quick Start Review my Dockerfile and docker-compose.yml against containerization best practices and list any violations.

Frequently Asked Questions about docker

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

FAQPage Schema
How do I write a production-ready Dockerfile?▼

Pin base image versions, use multi-stage builds to exclude build dependencies, copy dependency manifests before source files for cache efficiency, run as a non-root user, and use exec form for CMD and ENTRYPOINT.

How do I keep secrets out of Docker images?▼

Externalize configuration through environment variables, mounted config, or orchestrator settings. Use Compose secrets or platform-managed secrets for sensitive values, and never commit secrets to images or local files.

Should I use multi-stage builds in Docker?▼

Use multi-stage builds when build dependencies are not needed at runtime. This keeps final images smaller and reduces the attack surface by excluding compilers and build tooling from production images.

Does deploy.resources work in docker compose?▼

The deploy.resources field is Swarm and platform-specific behavior. Standard docker compose does not enforce it, so document which runtime actually applies these resource limits.

Why is my Docker build cache not working?▼

Cache invalidation usually happens when source files are copied before dependency manifests. Copy dependency manifests first, then source files, and keep .dockerignore updated to exclude VCS data, build output, and local dependencies.