Docker Compose Topology Inspector
Paste a docker-compose.yml (or open one from disk). You get a dependency diagram, a services overview and a list of problems with an explanation for each.
The tool could not be loaded. Check your connection and reload the page.
Result
Topology
Findings
Services
How it works
The YAML is parsed in your browser (YAML 1.2, including merge keys). Every service is normalised: short and long syntax of ports, depends_on, volumes, networks and environment end up in one shape.
In the diagram, entry points (services nobody depends on) are on the left and their dependencies to the right. A solid arrow means depends_on with condition: service_healthy, a dashed one only waits for the container to start. Coloured dots are networks, named volumes sit at the bottom and published ports are shown in yellow.
The checks cover host port collisions (including ranges and IP bindings), dependencies on unknown services and cycles, service_healthy without a healthcheck, undeclared networks and volumes, databases published on all interfaces, privileged containers, the Docker socket mounted into a container, host networking, dangerous capabilities, plaintext secrets and images without a version tag.
Limits: variables (${...}) are not resolved, and extends, include, profiles and multiple merged compose files are not evaluated. A healthcheck defined in the image's Dockerfile is not visible here.
When it helps
- Documenting a project: export the diagram as SVG for the README.
- Debugging a stack that will not start: port conflicts, unknown dependencies and cycles.
- Reviewing a compose file before using it on a server: exposed databases, privileged containers, docker.sock.
- Learning Compose: see how depends_on, networks and volumes connect services.
Frequently asked questions
// 01 Does it run or contact Docker?
No. It only reads the configuration you paste. No Docker daemon, registry or server is involved, and the file is not uploaded.
// 02 Why is depends_on without a condition reported for databases?
Plain depends_on only waits until the database container has started, not until the database accepts connections. Add a healthcheck to the database and use condition: service_healthy, or make the application retry.
// 03 What is wrong with "3306:3306"?
It publishes the database on every network interface of the host. On Linux, Docker manages its own iptables rules, so a firewall such as ufw does not block it. Bind it to localhost ("127.0.0.1:3306:3306") or drop the mapping, other containers on the same network reach the database by its service name.
// 04 Can I export the diagram?
Yes, as a standalone SVG that you can put in documentation, and the findings as JSON.
You may also need
Did this save you time?
The tools and simulations are free, ad-free and need no sign-up. If they helped you, you can send a contribution for coffee and new tools.
Donate via PayPalWhat happens to your data
Privacy policy (in Czech)- The tools process your input with JavaScript on your device. Nothing you paste is sent to the server, stored or logged.
- The exception is the SPF/DKIM/DMARC check: it asks public DNS (Cloudflare, Google as a fallback) directly from your browser. Only the domain name is sent.
- Analytics (only if you accept analytics cookies) records anonymous events such as "a tool was opened". Never your input or results.
- No ads or advertising scripts run on the tool and simulation pages.
Need a hand?
I build and maintain web applications in Laravel and PHP. If something on these pages is giving you trouble in a project, get in touch.
Get in touch