What problem does it solve? Working with Docker on someone else's machine risks breaking their containers, volumes, and stands, while opaque failures like hung commands, full disks, and failed registry logins waste hours of debugging. This Skill provides a disciplined operational pattern for running Docker safely on a shared host. ## Core Features & Use Cases - Safe daemon operations: Restart the Docker daemon via its own CLI, verify readiness with docker info, and inspect existing containers and restart policies before touching anything. - Disk space management: Measure space inside the Docker VM with docker system df, prune build cache by age and size limits, and remove only dangling volumes that lack compose project labels. - Failure diagnosis: Isolate whether a problem lives in the machine network, container network, or the daemon itself using a three-tier check, and avoid false 'hanging command' diagnoses caused by piped output. - CI/service registry access: Authenticate to registries from a service account by writing auth directly to an isolated DOCKER_CONFIG with an explicit DOCKER_HOST, and verify token scopes before a rollout depends on them. - Cross-platform builds: Build images for the production server architecture with buildx and a dedicated builder, without switching the owner's default builder. - Use Case: A CI runner on a teammate's Mac fails to push images. You create a temporary DOCKER_CONFIG, write the registry auth directly, set DOCKER_HOST to the user's socket, and build for linux/amd64 with a named builder — leaving the owner's environment untouched. ## Quick Start Ask the assistant to diagnose why a Docker command hangs on this machine and safely restart the daemon without affecting other containers.
