Loading…
0+ curated questions with the same answer shape every time: quick recap, deep dive, pitfalls, and follow-ups. Coverage includes .
Docker for Go applications is a distinct topic from Docker in general — Go's single static binary changes the optimization strategy. This module covers the Go multi-stage Dockerfile (build stage with the full Go toolchain → final stage with only the compiled binary, achieving images under 20 MB), distroless and scratch base images (the trade-off: no shell, no package manager, but zero extra attack surface — and why Go's static binary makes this feasible while Python or Java cannot), CGO and the GOOS=linux GOARCH=amd64 CGO_ENABLED=0 flags for cross-compilation in CI, Docker Compose for the local Go development stack (Go service + PostgreSQL + Redis + Kafka), running as a non-root user in a Go container, health checks for a Go HTTP server using /healthz, and the scenario: 'your Go binary works locally but segfaults in the container — what are the first three things you check?'
Full catalog
Topics are ordered for learning. Within each topic, rows are numbered 1–0 globally so you always know where you are. Collapse topics if you want a lighter view — use Expand all when you need the full list again.
Numbers 1–0 follow the order we recommend — click any row to open the full answer, or use the sticky Next link at the bottom of each page to go Q1 → Q0.