Docker Run Go Binary

The commands:

# Build the image from the Dockerfile
docker build -t myapp .

# Run the container
docker run -d -p 8080:8080 --name myapp-1 myapp
# -d: detached
# -p 8080:8080: host:container port mapping
# --name: the handle for logs/stops

# Verify
docker ps                    # the container is running
curl localhost:8080/health  # the app responds

docker logs myapp-1          # the app's stdout
docker stop myapp-1          # graceful stop
docker rm myapp-1             # remove

The binary's relationship to the container: the container IS the process (plus the isolation layers). The Go binary (CMD's target) runs as PID 1 inside the container — the container lives as long as the binary runs. When the process exits, the container exits — the lifecycle is one-to-one.

The port semantics: EXPOSE 8080 in the Dockerfile is DOCUMENTATION (the metadata that says 'this listens on 8080') — it does NOT make the port accessible. The -p 8080:8080 at run time is the actual mapping (the host port → the container port). Without -p, the app is unreachable from outside the container.

The Go-specific signals: a graceful shutdown needs the binary to handle SIGTERM (Go's os/signal) — the container stop sends SIGTERM, waits the grace period, then SIGKILL. Go's signal.NotifyContext integrates with this directly.