dockerfile

Installation
SKILL.md

🐳 Dockerfile

Where this fits

The container skills:

  1. dockerfile (this skill) — one image per service, plus the .dockerignore that defines its build context
  2. docker-compose — wires those images together with datastores, networks, volumes and health gates
  3. container-hardening — reviews how containers run wherever they run; its image findings (no USER, setuid binaries, a secret in a layer, an unpinned base) come back here to be fixed
  4. container-debug — when a container won't start, stay up or connect: reads the runtime's own record, matches the symptom, proves the cause, and routes the fix back to the skill that owns it
  5. docker-swarm — reviews or designs a Swarm cluster and the stack files docker stack deploy runs

Run this first. Compose orchestrates images; it cannot fix a bad one. A service whose image is already correct gets composed in minutes, and a service whose image is wrong fails in a way that looks like an orchestration bug.

The .dockerignore is part of this skill, not an afterthought. It defines the build context, and the build context determines what gets sent to the daemon, what invalidates the cache, and what secrets end up in a layer. A perfect Dockerfile over an unbounded context is still slow and still leaky.

It leans on two reference docs:

Installs
1
First Seen
Today