Enable Watchtower for all services #123
|
@ -2,13 +2,12 @@
|
|||
- name: watchtower container
|
||||
docker_container:
|
||||
name: watchtower
|
||||
image: containrrr/watchtower:1.4.0
|
||||
image: containrrr/watchtower:latest
|
||||
samsapti marked this conversation as resolved
Outdated
|
||||
restart_policy: unless-stopped
|
||||
env:
|
||||
WATCHTOWER_POLL_INTERVAL: 60
|
||||
networks:
|
||||
- name: external_services
|
||||
volumes:
|
||||
- /var/run/docker.sock:/var/run/docker.sock
|
||||
- "{{ docker_registry.volume_folder }}/auth/config.json:/config.json"
|
||||
samsapti marked this conversation as resolved
Outdated
valberg
commented
This means that This means that `docker-registry` should be run before `watchtower` right?
samsapti
commented
Yes, which is currently also the case. Yes, which is currently also the case.
|
||||
env:
|
||||
WATCHTOWER_LABEL_ENABLE: "true"
|
||||
WATCHTOWER_POLL_INTERVAL: "60"
|
||||
samsapti marked this conversation as resolved
Outdated
valberg
commented
Hvordan er det nu at services der skal opdateres bliver fundet hvis det ikke er via label? Hvordan er det nu at services der skal opdateres bliver fundet hvis det ikke er via label?
|
Loading…
Reference in a new issue
Let's pin this to a version instead of latest.
Why not latest?
Because I want to avoid confusion due to an unintended upgrade.
I don't fully agree. I think it's better to always use the latest version security-wise, especially when it has access to the Docker socket.
I agree, and we should strive to upgrade whenever a new version is available. But I don't want stuff to suddenly break behaviour without us knowing why.
I'll pin it then. GitHub supports RSS feeds for releases, maybe we could use that to be notified about new releases? We could set up notifications in our Matrix channel somehow.
https://github.com/containrrr/watchtower/releases.atom
Sounds like a great idea!