CodeConverter

5 of 5 free conversions left. Sign in for unlimited use.

About the Docker Compose Validator

The Docker Compose Validator checks a docker-compose.yml for the mistakes that most often break docker compose up: YAML errors and duplicate keys, services with no image or build, unquoted ports such as 22:22 that older YAML parsers read as a number, undeclared volumes and networks, depends_on cycles and unknown services, duplicate host ports, and bad restart, healthcheck and volume values. Quoting those number-like ports is the only change it applies.

How to use the Docker Compose Validator

  1. Paste your docker-compose.yml.
  2. Click Validate.
  3. Fix the errors and warnings in the findings table, or copy the corrected file if one is offered.

Frequently asked questions

Does it replace docker compose config?

No. It is a static check that cannot see your .env file, extends or include files, or your Docker daemon, so values that use ${VAR} interpolation are not checked. Run docker compose config as the final check.

What does the auto-fix change?

Only unquoted port mappings such as 22:22. YAML 1.1 parsers (Compose v1 and many tools) read them as the number 1342, although current Docker Compose reads them as text. They are quoted in a corrected copy; nothing else is rewritten, and comments are not preserved in that copy.

Are my data stored when I use the Docker Compose Validator?

The text you submit is processed in memory to produce the result and is not saved. Like any web server, Code Converter logs basic visit data (page, IP address and browser) but never the content you paste. Even so, use placeholder values instead of real production credentials.

Is the Docker Compose Validator free, and can I call it from a script?

It is free and only needs a free account (log in first). The same tool is available as a REST endpoint at POST /api/compose-validator; see the API documentation for the fields and examples.