Hono Dockerfile generator
Generate a production Dockerfile for a Hono app running on @hono/node-server, non-root and multi-stage.
Configure
Loading...
What this Dockerfile does
Nothing flagged
Good practice: Multi-stage build (5 stages)
Compilers, dev dependencies and source files stay in the build stages. Only the runtime artefacts are copied into the final image.
Good practice: Runs as node, not root
A container escape from a root process is a host root process. Dropping privileges is the cheapest hardening step there is.
Good practice: .dockerignore keeps secrets out of the build context
`.git`, `.env` and local dependency folders never reach the daemon, so they cannot end up in a layer or in `docker history`.
Good practice: Dependency cache persists across builds
BuildKit cache mounts keep the package manager store outside the image. Rebuilds after a lockfile change reuse everything already downloaded, and the cache adds nothing to the final size.
Good practice: Healthcheck defined
Docker, Compose and Easypanel can tell the difference between a running process and a working app, and restart it when it wedges.
Note: Requires BuildKit
BuildKit is the default builder in Docker 23 and later. On anything older, export `DOCKER_BUILDKIT=1` before building.
Note: Alpine uses musl, not glibc
Smallest possible image, but packages with prebuilt native binaries — sharp, canvas, bcrypt, better-sqlite3, Prisma engines — may have to compile from source or fail outright. Switch to Debian slim if a native module misbehaves.
Note: Estimated image size: ~60–120 MB
A rough band for the final stage, before your own dependencies. Run `docker images` after a build for the real number.
How to use it
Everything runs locally. Nothing is uploaded, and no account is needed.
Drop the files into your project root
Every generated file belongs next to your package manifest — the Dockerfile references paths relative to the build context, so nesting them in a subfolder breaks the COPY lines.
Build the image
docker build -t hono .Run it
docker run --rm -p 3000:3000 honoOr bring up the whole stack
docker compose up --build