Dockerfile checker for Bex
Paste a Dockerfile, or load a sample. Each finding points at a line where the file assumes something Bex's build or runtime does differently, such as a port below 1024, a hard-coded `PORT`, a `HEALTHCHECK` Bex never runs, or a build secret it never passes. Each one links to the docs section that explains the behavior.
Every rule comes from a snapshot of Bex's own build and operator sources, pinned to the revision shown under the report. The checker reports nothing without a consequence on Bex, so general Dockerfile style is out of scope.
These tools run entirely in your browser. Nothing you paste or drop is uploaded, stored, or sent to analytics.
Up to 256 KiB and 2000 instructions; larger files are refused, not truncated. Press Ctrl+Enter (⌘+Enter on a Mac) to check without waiting.
Paste a Dockerfile or pick a sample to see the report.
Deploy it on Bex
Bex builds the Dockerfile from your repository with `runtime: docker`, or deploys a prebuilt image. The Docker deploys guide covers both, plus private registries and the container contract these findings come from.
What this checker does not check
- Whether the build succeeds: no command runs and no image is built.
- Whether base images exist or can be pulled, including private registry credentials.
- The size of the resulting image.
- How the app behaves once it runs, such as which port it really listens on.
- Blueprint settings such as `dockerfilePath`, `dockerContext` or `healthCheckPath`. Check them with the render.yaml checker.
The rules' bex revision appears once the checker has loaded.