Skip to main content
Yoryantra
Home/Tools
← Back to Tools

Docker Compose Service Dependency Visualizer

Map Compose service relationships while separating startup dependencies from network and environment hints.

Paste a full docker-compose.yml file or just the services block.

Graph Settings

Extracted from

servicesdepends_onnamespace refslinksportsnetworksenvironment

Checks

YAML is parsed structurally in the browser. Compose interpolation, profiles, extends, include files, and runtime resolution are not executed here.

Output

Dependency graph output will appear here.
Compose text is parsed in your browser. Nothing is sent to Docker, a registry, or a Yoryantra server by this page.

Read the graph as several different kinds of relationship

A Compose file can describe startup ordering, shared namespaces, published ports, network membership, and application-level connection strings. Those signals are related, but they do not mean the same thing. The graph keeps formal depends_on edges separate from legacy links, service namespace references, and environment-derived hints.

That distinction matters when debugging startup problems. A database hostname inside DATABASE_URL suggests an application connection, but it does not create Compose startup ordering by itself.

What Compose actually guarantees for depends_on

Short-form depends_on establishes dependency order, but it does not wait for a service to become healthy. Long syntax can require service_healthy or service_completed_successfully. The parser preserves those conditions so a graph does not flatten every dependency into the same promise.

Application retries still matter. Even a well-ordered container startup is not a substitute for handling delayed network availability, database recovery, or an unhealthy dependency.

Signals that are informative rather than authoritative

  • Environment hints: service names found inside values such as database or Redis URLs are inferred application relationships.
  • links: these can express service reachability aliases, but modern Compose networking normally makes explicit links unnecessary.
  • network_mode / ipc / pid service references: these share another service's namespace and are shown separately from startup dependencies.
  • ports: entries under ports publish container ports to the host; they are not service-to-service dependency declarations.

Where this browser analysis stops

The YAML document is parsed, but Compose interpolation, profile activation, extends, external include files, image metadata, and live container state are not resolved. Treat the graph as a structural reading of the pasted document, then confirm runtime behavior with docker compose config, health status, and logs.

Docker's Compose service reference is the useful authority for depends_on conditions and service-level networking behavior: Docker Compose services reference.

Mermaid output is intentionally presentation-only

Mermaid output gives every service a generated node identifier and keeps the original service name as a quoted label. This avoids collisions when names contain punctuation and prevents a service name from being interpreted as Mermaid syntax.