:latest or :version for supporting services?

1. Nginx Proxy Manager

   1 662 26,129 9.0 JavaScript

   Docker container for managing Nginx proxy hosts with a simple, powerful interface

   

   Prime example: Nginx Proxy Manager is often recommended in the sub. The latest minor release came with breaking changes (so already ignoring semver). I bet you many people were running on latest and then had broken stuff: https://github.com/NginxProxyManager/nginx-proxy-manager/releases/tag/v2.10.0

2. Civic Auth

   www.civic.com featured

   Auth in Less Than 5 Minutes. Civic Auth comes with multiple SSO options, optional embedded wallets, and user management — all implemented with just a few lines of code. Start building today.

   

3. docker-lock

   2 3 429 0.0 Go

   Discontinued Automatically manage image digests in Dockerfiles, docker-compose files, and Kubernetes manifests by tracking them in a separate Lockfile

   

   I do both! I tag my services with :latest, then use docker-lock. It scans your docker and docker-compose, generates a lock file and adds the current sha to git. That lets me freely update because I can always go get the previous version from git, rollback, and pin the version for that specific container if there is a problem. It really is the best of both worlds.

4. renovate

   3 13 - -

   You commit your docker-compose.yml file(s) to a GitHub repo (don't commit secrets!!), then add the Renovate App to your repo, merge the onboarding PR, then you'll get PRs when an image is updated.

Suggest a related project