Docker Compose Validator
Check a Compose file in your browser for undefined services, volumes, and networks before you run it.
This tool handles input and primary processing in your browser and is designed not to send the input to QuickKit’s server.
Avoid live production secrets; use dummy or masked data where possible. Data handling details
How it works
Paste a Compose file. The structural checks match what `docker compose config` reports as an invalid project: a service with neither image nor build, a depends_on naming an undefined service, and a volumes or networks entry naming something the file never declares. Everything runs in your browser and nothing is uploaded. This does not resolve extends, include, env_file, profiles, or ${VARIABLE} interpolation, and it never contacts a registry or a Docker daemon — so it cannot tell you whether an image exists or whether the stack will actually start.
This tool parses the subset of YAML that Compose files use. Anchors, aliases, merge keys, tags, and multiple documents in one file are reported by name rather than misread, because a parser that guessed at them could give a confidently wrong verdict.
Structure only. No registry lookup, no daemon, no guarantee the stack will start.