Docker Ops Playbook

The problem

Managing Docker containers manually often leads to forgotten volumes, orphaned networks, and disk space exhaustion. Developers frequently struggle with the exact syntax for backup/restore operations and resource limit enforcement during runtime.

What it does

• Executes standard lifecycle operations for containers, images, volumes, and networks.
• Performs safe disk space reclamation by pruning builder caches and unused images.
• Handles volume data backups and restores using temporary helper containers.
• Manages Docker Compose stacks including service-specific logs and teardowns.
• Implements runtime resource constraints for memory, CPU, and PID limits.

Frameworks & tools

Docker Engine, Docker Compose, and Linux/Unix shell environments.

Why this beats prompting it yourself

This skill enforces a specific operational sequence, starting with inventory checks to prevent accidental overrides. It uses hardened defaults like restart policies and specific logging flags that are often missed in generic AI prompts.

Use cases

• Debugging a failing service by attaching an interactive shell and tailing logs.
• Reclaiming gigabytes of disk space by safely pruning the Docker subsystem.
• Moving data between volumes via tarball backups for maintenance windows.
• Deploying containers with strict resource limits to prevent memory leaks from crashing the host.

Known limitations

Does not support Kubernetes orchestration or daemon-level security hardening. Not intended for authoring complex Dockerfiles from scratch.