Docker Container Ops

The problem

Managing Docker lifecycles manually often leads to orphaned volumes, bloated disk usage, and complex troubleshooting when containers exit with cryptic codes. Developers waste time on repetitive multi-stage build commands and UID/GID mapping issues that break file permissions.

What it does

• Installs and configures Docker Engine, Buildx, and Compose on fresh environments.
• Manages the full image lifecycle including multi-stage builds, tagging, and registry pushes.
• Handles complex container operations, network bridging, and volume persistence.
• Automates system maintenance to reclaim disk space from dangling images and stale volumes.
• Deploys and manages specialized stacks like Hermes Agent, Camofox, and qi-engine.

Why this beats prompting it yourself

This skill moves beyond basic CLI syntax by implementing best practices for container health monitoring and resource recovery. It handles project-specific configurations like Hermes s6-overlay supervision and specific UID/GID mapping that generic prompts often overlook.

Use cases

• Deploying complex stacks with local volume mounting and host network modes.
• Debugging silent container failures by inspecting exit codes, OOM events, and layer history.
• Automating environment cleanup to fix "no space left on device" errors.
• Scaling and rebuilding individual microservices within a larger Compose file.

Known limitations

Docker is not pre-installed by default and requires an initial setup script execution. Host network mode operations ignore standard port mapping directives.