>_ tools --compose

Docker Compose Validator

Paste a docker-compose.yml and get a Compose-aware lint - indentation, obsolete version, volume mounts, service ordering, healthchecks, and the WordPress/Nginx/Redis gotchas - plus one-click stacks. Everything runs in your browser; nothing is uploaded.

PRESETS

one click fills the editor
0 lines · 0 B

LINT REPORT

Honest scope: this is a static, Compose-aware validator running in your browser - it catches config mistakes and common-sense compose mistakes before docker compose up. It does not run Docker, so it cannot catch every runtime error.
no server · static compose-aware lint · test with docker compose config before deploying
.htaccess → Nginx Converter The nginx.conf your compose stack serves through. Debug Log Analyzer When the stack runs but WordPress misbehaves. JSON Formatter The other half of YAML: inspect API payloads. SQLite ⇄ MySQL Converter Migrating the database your db service hosts.

>_ FAQ

What does the Docker Compose validator check?

It is Compose-aware, not just YAML syntax: indentation/tabs, the obsolete version field, volume mounts (single-path, undeclared volumes), service ordering and healthchecks, and WordPress/Nginx/Redis specific gotchas.

Why does a DB need a healthcheck?

A web service that depends on a database can start before the DB is ready, causing connection errors. A healthcheck plus depends_on: condition: service_healthy makes the web service wait.

Is this a full Docker validator?

It is a static, Compose-aware lint that runs in your browser. It catches config mistakes before docker compose up, but does not run Docker, so it cannot catch runtime-only problems.