Docker Compose Validator
Check a Docker Compose file for typos, missing images, undeclared volumes and networks, clashing ports, broken depends_on links and risky settings.
How to check a Compose file
Paste your compose.yaml
Paste or type your compose.yaml into the box, or press Try an example.
Read the problems
Each one names the service and setting it is about.
Fix and paste again
The check runs as you type.
When to use Docker Compose Validator
docker compose up fails with an error that does not say which service is wrong.
A setting seems to be ignored and you suspect a misspelled key in compose.yaml.
Tips for a better Docker Compose Validator result
Read the did-you-mean suggestions carefully: a misspelled key is ignored by Compose without any error.
Quote port mappings such as "22:22", since some YAML parsers read unquoted values with colons as numbers.
Docker Compose Validator: limits and what to check
Variables filled in from the environment are checked as written, so a value that only breaks after substitution will not be caught.
Settings added in very recent Compose releases may be flagged as unknown until this list is updated.
About Docker Compose Validator
Catch Compose mistakes before docker compose up does, or worse, before a setting is silently ignored. Unknown keys get a did-you-mean suggestion, so enviroment points you to environment. Services are checked for an image or build, depends_on targets, declared volumes and networks, clashing host ports and restart policies.
FAQs
Is the version key a problem?
No, but Compose v2 ignores it and prints a warning, so it can go.
Why warn about passwords in the file?
Values written into compose.yaml end up in version control. An .env file or Docker secrets keep them out.
Does it read my .env file?
No. Variables written with a dollar sign and braces, such as TAG, are left as written. Run docker compose config on your machine to see the final file.