All Dockerizers

Go Dockerfile generator

Generate a production Dockerfile for a Go service — a statically linked binary cross-compiled without QEMU, in an image with nothing else in it.

Configure

Used for the image tag, the compose service and the OCI labels.
The port the app listens on inside the container. Keep it above 1024 so the process can bind it without root.
The package path passed to `go build`. Use `.` if main.go is at the project root.
Adds the database to docker-compose.yml with a healthcheck, a named volume and a DATABASE_URL wired into the app.
Adds Redis to docker-compose.yml and exposes REDIS_URL to the app.

Loading...

What this Dockerfile does

Nothing flagged

  • Good practice: Multi-stage build (2 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 65532:65532, 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.

  • Good practice: Statically linked, no runtime needed

    CGO_ENABLED=0 produces a binary with no dynamic dependencies at all, which is why the runtime image can be empty.

  • Good practice: Reproducible, stripped binary

    `-trimpath` removes absolute build paths and `-ldflags="-s -w"` drops the symbol table and debug info. Together they usually take a quarter off the binary size.

  • Note: Requires BuildKit

    BuildKit is the default builder in Docker 23 and later. On anything older, export `DOCKER_BUILDKIT=1` before building.

How to use it

Everything runs locally. Nothing is uploaded, and no account is needed.

  1. 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.

  2. Build the image

    docker build -t go-app .

  3. Run it

    docker run --rm -p 8080:8080 go-app

Go in Docker

Related generators

Rust

Go & Rust

FastAPI

Python

Node.js

JavaScript

.NET

JVM & .NET
map illustration

Join 145,000+ self-hosters.

Free plan available. No credit card required.

Install Easypanel