How to use Dockerfile and Compose Linter
- Paste a Dockerfile, Compose configuration or both in their labelled inputs.
- The static reports update as you edit their respective inputs.
- Review each reported line, rule and unsupported construct before using the file. The page does not build images or start containers.
Example: Dockerfile and Compose Linter
Inspect supported Dockerfile or Compose checks, filter findings and download the full report.
Options
- Filter observations by words
- Use up to 100 characters to filter the visible table by document, rule or observation text. The JSON download keeps all reported findings, up to the 200-finding cap, and the count of any additional omitted observations.
- Dockerfile
- Static Dockerfile rules inspect FROM digests, secret-like ARG/ENV names, stage USER choices, and separate apt/apk update/install RUN layers. Up to 100,000 characters and 5,000 lines.
- Compose YAML
- Bounded JSON-compatible YAML parsing checks duplicate keys, top-level and service keys, image digests, privileged mode and host networking. Up to 100,000 characters, 5,000 lines, 40 levels and 12 aliases.
Supported inputs and limits
- Each document is limited to 100,000 characters and 5,000 lines.
- UFT-DockerRules 1.0 and UFT-ComposeKeys 1.0 report up to 200 findings and state how many were omitted.
- Compose YAML uses js-yaml 5.4.1 JSON_SCHEMA with duplicate keys refused, a maximum depth of 40, 12 alias references and 20,000 visited nodes.
- The rules inspect immutable image digests, selected Dockerfile instructions, secret-like variable names and selected Compose keys, privilege and network settings.
More details
It does not build images, resolve variables or files, run containers, validate the complete engine grammar or certify security.
Text filtering changes the visible findings only; the download keeps the full report.
Checks remain within the existing dated rules.
This is not hadolint, a container build or a complete security review.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
Static review and engine validation serve different tasks
Line checks can point out a moving image reference or a setting worth revisiting. They cannot inspect an included file or test a container's runtime behavior. Review the observations alongside the Dockerfile and Compose specifications, then validate the actual configuration in its intended environment.
Questions about Dockerfile and Compose Linter
Does a clean report mean the configuration will run?
No. The page checks only its listed text rules. It does not resolve files, environment values, images, networks or the target engine's complete configuration grammar.
Why is an image tag reported?
A tag can point to a different build later, including a tag that names a version. The rule looks for an immutable sha256 digest. It does not verify the image's contents or choose a version for you.
Does the page display secret values?
The report identifies a secret-like variable name or its line without repeating its value. It cannot recognise every possible secret, so remove live credentials before preparing a sample.
Are privileged settings always an error?
They are configuration observations that need context. A static page cannot establish the permissions or isolation your particular workload requires.