Dockerfile Linter
Client-side heuristics for common Dockerfile issues
API executable
Overview
ID: dockerfile-linter
Category: data
Call this tool over HTTP with POST /execute/dockerfile-linter. Path, headers, body fields, sample responses, and errors are documented below.
Endpoint
POST
/api/v1/execute/dockerfile-linterAuthenticate with X-API-Key or Authorization: Bearer. See Authentication.
API reference
Path, header, and body fields accepted by this execute call.
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| tool | path | string | Yes | Tool identifier used in the execute path. Example: dockerfile-linter |
| X-API-Key | header | string | Yes | Your IT-ToolBox API key. Authorization: Bearer is also accepted. Example: YOUR_API_KEY |
| Content-Type | header | string | Yes | Must be application/json for execute requests. Example: application/json |
| input.dockerfile | body | string | Yes | Argument for Dockerfile Linter. Example: FROM alpine RUN apk add curl |
Code examples
shell
curl -X POST /api/v1/execute/dockerfile-linter \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"input": {
"dockerfile": "FROM alpine\nRUN apk add curl"
}
}'Tool UI
Open the interactive experience to try the tool without writing HTTP clients.
Open tool UI