Dockerfile Generator

Generate a Dockerfile for Next.js, Node.js, Python, or a static site, following common multi-stage build best practices for smaller, more secure images.

StackNode versionPort

Dockerfile

FROM node:22-alpine AS deps
WORKDIR /app
COPY package.json package-lock.json ./
RUN npm ci

FROM node:22-alpine AS builder
WORKDIR /app
COPY --from=deps /app/node_modules ./node_modules
COPY . .
RUN npm run build

FROM node:22-alpine AS runner
WORKDIR /app
ENV NODE_ENV=production
RUN addgroup --system --gid 1001 nodejs && adduser --system --uid 1001 nextjs
COPY --from=builder /app/public ./public
COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static
USER nextjs
EXPOSE 3000
ENV PORT=3000
CMD ["node", "server.js"]

.dockerignore

node_modules
.next
.git
.env
npm-debug.log
dist
__pycache__
*.pyc

The Next.js template assumes output: "standalone" is set in next.config, which is what makes the small final runner image possible.

Ad space

Frequently asked questions

Why does the Next.js template use multiple FROM stages?+

Multi-stage builds keep the final image small by discarding build-only dependencies (like devDependencies and the full node_modules tree) and only copying the compiled output into the final runtime image.

Do I need to change anything for it to work?+

The Next.js template assumes output: "standalone" is set in next.config; the Node and Python templates assume standard package.json/requirements.txt setups. Adjust the start command if yours differs.

Does this run the container for me?+

No, it only generates the Dockerfile text. Build and run it yourself with docker build and docker run, or use the matching Docker Compose Generator tool.