Dockerfile Generator

Generate a production-ready Dockerfile with multi-stage builds, an Alpine base, a non-root user and layer caching, for Node, Python, Go, Rust or Java.

Pay by wallet (x402) AI-generated dockerfile-generate

Example

Input

{
  "language": "en",
  "framework": "express"
}

Answer

{
  "stages": [
    "dependencies",
    "builder",
    "runtime"
  ],
  "language": "en",
  "framework": "express",
  "build_args": [],
  "dockerfile": "# Stage 1: Dependencies\nFROM node:18-alpine AS dependencies\nWORKDIR /app\nCOPY package*.json ./\nRUN npm ci --only=production && npm cache clean --force\n\n# Stage 2: Builder\nFROM node:18-alpine AS builder\nWORKDIR /app\nCOPY package*.json ./\nRUN npm ci\nCOPY . .\nRUN npm run build --if-present\n\n# Stage 3: Runtime\nFROM node:18-alpine AS runtime\nWORKDIR /app\n\n# Install dumb-init for proper signal handling\nRUN apk add --no-cache dumb-init\n\n# Create non-root user\nRUN addgroup -g 1001 -S nodejs && adduser -S nodejs -u 1001\n\n# Copy production dependencies from dependencies stage\nCOPY --from=dependencies --chown=nodejs:nodejs /app/node_modules ./node_modules\n\n# Copy application code from builder stage\nCOPY --from=builder --chown=nodejs:nodejs /app/package*.json ./\nCOPY --from=builder --chown=nodejs:nodejs /app/dist ./dist\nCOPY --from=builder --chown=nodejs:nodejs /app/public ./public\n\n# Switch to non-root user\nUSER nodejs\n\n# Expose port\nEXPOSE 3000\n\n# Healthcheck\nHEALTHCHECK --interval=30s --timeout=3s --start-period=5s --retries=3 \\\n  CMD node -e \"require('http').get('http://localhost:3000/health', (r) => {if (r.statusCode !== 200) throw new Error(r.statusCode)})\"\n\n# Use dumb-init to handle signals properly\nENTRYPOINT [\"dumb-init\", \"--\"]\n\n# Start application\nCMD [\"node\", \"dist/index.js\"]",
  "multi_stage": true,
  "security_notes": [
    "Non-root user (nodejs:1001) runs the application",
    "Multi-stage build reduces final image size by excluding dev dependencies",
    "Alpine Linux base image minimizes attack surface",
    "dumb-init handles PID 1 and signal forwarding correctly",
    "Only production dependencies copied to final stage",
    "Read-only filesystem recommended in production via security context",
    "No package manager or build tools in final image",
    "HEALTHCHECK validates application responsiveness"
  ],
  "estimated_image_size": "120-150MB",
  "dockerignore_recommended": [
    "node_modules",
    "npm-debug.log",
    ".git",
    ".gitignore",
    ".env",
    ".env.local",
    ".DS_Store",
    "dist",
    "build",
    ".next",
    "coverage",
    ".nyc_output",
    "*.log",
    ".vscode",
    ".idea",
    "*.swp",
    "*.swo",
    "*~",
    ".eslintcache",
    "yarn-error.log",
    ".npm",
    ".eslintignore",
    "README.md",
    "LICENSE",
    ".editorconfig",
    "docker-compose*.yml",
    "Dockerfile*",
    ".dockerignore",
    ".github",
    ".gitlab-ci.yml",
    ".circleci",
    "test",
    "tests",
    "jest.config.js",
    "vitest.config.js",
    ".mocharc.json"
  ]
}

Inputs

Field	Type	Required	What it is
`alpine`	boolean	No	—
`language`	string	Yes	—
`framework`	string	No	—
`multi_stage`	boolean	No	—

Output fields

How reliably each field appears in a successful answer.

Field	Type	Appears
`stages`	array	Always (present in every successful answer)
`dockerfile`	string	Always (present in every successful answer)
`security_notes`	array	Always (present in every successful answer)
`estimated_image_size`	string	Always (present in every successful answer)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "dockerfile-generate",
    "inputs": {
      "language": "en",
      "framework": "express"
    },
    "max_price_cents": 5
  }'

{
  "tool": "strale_execute",
  "arguments": {
    "slug": "dockerfile-generate",
    "inputs": {
      "language": "en",
      "framework": "express"
    },
    "max_price_cents": 5
  }
}

import { Strale } from "straleio";

const strale = new Strale({ apiKey: process.env.STRALE_API_KEY! });
const result = await strale.do({
  capability_slug: "dockerfile-generate",
  inputs: {
    "language": "en",
    "framework": "express"
  },
  max_price_cents: 5,
});

import os
from straleio import Strale, DoRequest

strale = Strale(api_key=os.environ["STRALE_API_KEY"])
result = strale.do(DoRequest(
    capability_slug="dockerfile-generate",
    inputs={
        "language": "en",
        "framework": "express",
    },
    max_price_cents=5,
))

# No account. The first request answers 402 with the price in USDC;
# an x402 client pays it from your wallet and repeats the request.
curl -i 'https://api.strale.io/x402/v2/dockerfile-generate?language=en&framework=express'

Limitations

Project-specific build requirements can be missed
Generated Dockerfiles follow best practices but may not account for project-specific build requirements or private registries
What to do instead: Test the generated Dockerfile in a CI pipeline and adjust base images, build args, and secrets as needed