Inspect a Compose file for dependency cycles, host port collisions, privileged containers and the unquoted port mappings a YAML 1.1 parser misreads.
Waiting for a compose file
Nothing is run and no daemon is contacted.
The findings appear here
Published datastores, literal secrets, bind mounts that will not exist elsewhere, and dependencies that do not wait.
One finding worth taking seriously even when the stack is local: publishing a database port binds it to every interface by default, and Docker writes its own iptables rules, so a host firewall often does not stop it. On a cloud host that is the open internet. Binding to 127.0.0.1: keeps it reachable from your machine and nowhere else — and services in the same file can always reach each other by name without publishing anything at all.
Docker Compose Inspector runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
Compose has three classes of problem and they need different treatment. Structural ones are definite: a dependency cycle will never start, two services claiming the same host port will collide, a `depends_on` naming a service that does not exist is a typo. Those are reported as errors.
The YAML ones are subtler. An unquoted `22:22` is the integer 1342 under YAML 1.1's sexagesimal rule, which Compose's Go parser implements — so the guidance to quote port mappings is real and not superstition. This inspector applies the 1.1 production precisely: `22:22` is flagged, `8080:80` is not, because the second is not a valid sexagesimal number and cannot be misread. Most linters flag every unquoted port and train you to ignore them.
The security ones are judgements with context. `privileged: true` removes essentially every container boundary; mounting the Docker socket gives the container control of the host daemon, which is root-equivalent. Both are sometimes necessary and always worth knowing about, so each says what it grants rather than just that it is bad.
There is also a note for `version:` at the top, which the Compose Specification dropped. It is harmless but marks a file written for Compose v1, which usually means other conventions in it are out of date too.
Nothing is executed and the Docker daemon is never contacted.
Only when the mapping is a valid YAML 1.1 sexagesimal number — `22:22` becomes the integer 1342, while `8080:80` cannot be misread. Quoting all of them is a reasonable habit; this tool flags only the ones that genuinely bite, so the warnings mean something.
It gives the container control of the host's Docker daemon, which can start a privileged container with the host filesystem mounted. It is root on the host with extra steps. Sometimes necessary for CI runners and worth understanding before you do it.
Because Compose cannot order the startup and refuses to start. It is not a style preference — the stack does not come up until the cycle is broken.
Yes. The Compose Specification dropped it; current versions ignore it and may warn. It is harmless in itself but usually indicates a file written against Compose v1.
No. The file is parsed as YAML in your browser. No command is run and the local daemon is never contacted.