Ask Claude to Write a Dockerfile for Your Project by Reading the Codebase

Writing a Dockerfile from scratch means knowing the right base image, the right build steps, which files to copy, which ports to expose, and how to keep the image small. Claude can figure all of that out by reading your project.

> read my project and write a production-ready Dockerfile

Claude inspects your package.json, composer.json, requirements.txt, or whatever dependency files exist, checks your build scripts, reads your config to find the port and entry point, and generates a Dockerfile that matches your actual setup — not a generic template.

You can be specific about what you need:

> write a multi-stage Dockerfile that builds the frontend with npm
> and serves the PHP app with nginx and php-fpm

> create a Dockerfile optimized for small image size — use alpine
> base images and minimize layers

> write a Dockerfile and docker-compose.yml for local development
> with hot reload, a database, and Redis

Claude reads your code to make decisions a generic template can't:

• Base image — picks the right version based on your runtime requirements
• Dependencies — installs only what your project actually uses
• Build steps — runs your actual build commands in the right order
• Multi-stage builds — separates build-time and runtime dependencies to keep images lean
• Security — runs as a non-root user, copies only necessary files, uses .dockerignore patterns

Ask Claude to generate a .dockerignore file at the same time:

> also create a .dockerignore that excludes tests, docs, node_modules,
> and anything else that doesn't belong in the production image

If you already have a Dockerfile that works but is bloated or slow, paste it and ask Claude to optimize:

> this Dockerfile works but the image is 2GB and builds take 10 minutes —
> optimize it for size and build speed

A good Dockerfile is project-specific — let Claude read yours and build it right.

via Claude Code