pin filebrowser, couchdb, statping to explicit versions instead of floating beta/dev/untagged
Same category of risk as the gitea :nightly issue: floating dev/beta tags let watchtower silently pull unvetted upstream builds. couchdb had no tag at all (implicit :latest); filebrowser and statping only publish beta/dev channels upstream so pinned to the exact version in use rather than a moving target.
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
services:
|
||||
couchserver:
|
||||
image: couchdb
|
||||
image: couchdb:3.5
|
||||
container_name: couchdb
|
||||
restart: always
|
||||
labels:
|
||||
|
||||
Reference in New Issue
Block a user