Dockerfile Validator
Check a Dockerfile for the mistakes that break builds, with the exact line of each problem.
- Runs in your browser No upload — everything runs on your device.
- No sign-up, no watermark Free to use, no account needed.
- Files never uploaded Nothing leaves your device.
- 5,400+ tools, one site File, unit and currency tools in one place.
Check a Dockerfile for the mistakes that break builds, with the exact line of each problem. Paste the file and the tool reads it instruction by instruction: it requires a FROM as the first instruction, rejects unknown instructions, checks that COPY and ADD have both a source and a destination, that RUN, CMD and ENV have arguments, and that EXPOSE ports are numbers between 1 and 65535. It also warns about the softer problems — a base image with no tag, the deprecated MAINTAINER instruction, and ADD fetching remote files or auto-extracting archives where COPY would be safer. The result is a simple verdict plus a list of issues, each with its line number and severity, and a count of the instructions found. A file with no errors is reported valid. Everything runs in your browser, so your Dockerfile never leaves your device and nothing is stored.
How to use Dockerfile Validator
- Paste your text type, paste (Ctrl+V) or drop a .txt file into the box above.
- Click Convert the tool runs entirely in your browser — nothing is uploaded.
- Read your results they appear below the tool as soon as the conversion finishes.
- Download the result save it for your records.
- Convert another clear the box and paste new text — no sign-up, no limits.
Format facts
| Input | Any plain text, or a .txt file (dropped or browsed). |
|---|---|
| Engine | Built-in browser engine |
| Category | Developer Tools |
Limits
- Browser processing has practical limits: files over 200 MB (or very long media) may be too large for your device. You will get an honest “too large” message, never a fake result.
- Pasted content is handled as plain text — formatting from documents is not preserved.
Frequently asked questions
What does the validator check?
That FROM is the first instruction, that every instruction is a real Dockerfile instruction, that COPY and ADD have a source and a destination, that RUN, CMD and ENV have arguments, and that EXPOSE ports are valid numbers.
What is the difference between an error and a warning?
An error means the file is wrong and the build will fail or misbehave — a missing FROM, an unknown instruction, or an invalid port. A warning means the file works but could be better, such as a base image with no version tag.
Why does it warn about an untagged base image?
FROM node with no tag means the latest image, which changes over time. Pinning a version such as node:20 makes the build reproducible.
Does a valid result mean the image will build?
Not quite. It means the Dockerfile itself has no structural mistakes. The build can still fail if, for example, a file it copies does not exist or a package cannot be installed.
Was this tool helpful?
Thanks — your feedback helps us improve this tool.
Sorry it didn’t help — tell us what went wrong and we’ll fix it.