Custom Dockerfile
Bring your own container image build (runtime_kind: custom_dockerfile) when you need full control over the OS, packages, and entrypoint.
Requirements
- A valid Dockerfile at the repository root or under the configured root directory
- An application process that listens on the container listen port you declare in runtime options (the edge proxy targets this port inside the container network)
- A health check path suitable for HTTP probing once the container is up
Custom images are built without mutating your source tree—plan multi-stage builds and dependency caching inside the Dockerfile itself.
Example skeleton
Dockerfile
FROM node:20-bookworm-slimWORKDIR /appCOPY package*.json ./RUN npm ci --omit=devCOPY . .ENV NODE_ENV=productionEXPOSE 3000CMD ["node", "server.js"]
See also
- Node.js services— prefer when a stock Node start command is enough
- Environments & variables— inject configuration at deploy time