Docker Toolkit

Docker Compose Validator catches the mistakes that only normally surface at docker compose up — undefined services, invalid ports, undeclared volumes/networks — and Dockerfile Linter does the same for the image build itself: unpinned tags, missing USER, and other best-practice gaps. Docker Compose Formatter cleans up indentation while preserving comments, and Docker Compose Visualizer turns the file into a diagram of service start order, networks, and volumes — the fastest way to actually see how a multi-service stack fits together instead of tracing YAML by eye. Running more than one compose file together (a base plus an override, or several -f flags)? Docker Compose Merge Visualizer shows the fully merged result and exactly which file set each field. That merged (or single) file still has ${VAR} placeholders and shorthand fields Compose expands silently at runtime — Compose Config Inspector resolves the variables against a .env file and shell overrides and expands ports/volumes/environment/build into the long form Compose actually runs against. Once containers are actually running, Docker Network Inspector reads docker network inspect output and explains each network in plain English — including why containers on the default bridge can't find each other by name.