Find structure and type errors
Paste a single YAML document. A misspelled service property or the wrong value type is reported at its schema path. Extension keys beginning with x- follow the upstream schema rules.
Validate the final resolved configuration
A service dependency may be provided by another Compose file or an include. This tool checks only the document you supply. On your machine, use docker compose config with the same files, profiles and environment as deployment.
Read the service dependency graph
The graph preserves service_started, service_healthy and service_completed_successfully conditions from depends_on. It shows a declared relationship, not evidence that a health check will pass or that a service will start. The same source can be copied to the Mermaid editor or exported as an image.
Schema source and license: Compose Specification, Apache-2.0. Third-party notices.
Frequently asked questions
Is this equivalent to docker compose config?
No. This checks the document schema, local depends_on names, selected service: references and dependency cycles in one file. It does not merge files, expand variables, resolve includes or extends, select profiles, inspect images or run Docker. Validate the resolved configuration with your installed Compose version.
Which Compose version does it support?
The tool uses a pinned revision of the upstream Compose Specification Schema, linked below the results. Your installed Docker Compose release may support a different feature set.
What does the service graph show?
Arrows point from each service to its prerequisite. Long-form depends_on conditions remain visible, optional dependencies use dashed arrows, and network_mode, ipc and pid service references are included. Missing references and local cycles are reported. Copy the Mermaid source, open it in the Mermaid editor or export the diagram as SVG or PNG. Profiles, includes and interpolation are not resolved, so the graph describes only the supplied file.