One container is easy. The trouble starts at six, when you no longer remember which one holds the database and why the image is 1.2 GB.
These tools answer those questions, and all of them are free or open source.
Docker Compose
One file that describes the whole local environment; still the most useful thing in the ecosystem.
docs.docker.com/composePortainer
A web UI for containers, volumes and logs when you are not in the mood for the CLI.
portainer.ioLazydocker
All of the above inside the terminal, with logs and stats one keystroke away.
github.com/jesseduffield/lazydockerDive
Shows layer by layer why your image is huge, which usually turns out to be one COPY.
github.com/wagoodman/diveTraefik
Routes domains to containers and renews TLS certificates without you thinking about it.
traefik.ioWatchtower
Updates running containers when a new image is published; use it deliberately, not everywhere.
containrrr.dev/watchtowerIf you add only one, make it Dive: shrinking images is the cheapest performance win in any deployment pipeline.
Need it built, not just chosen?
Web apps, APIs, infrastructure and interfaces. Freelance from Barcelona, working with clients anywhere.
Leave a Reply