Introduction
Deprecation Notice
Watchtower v2 Legacy Notification Deprecation
Watchtower has a number of legacy notification configuration options that will be removed with the release of Watchtower v2:
Migration to the NOTIFICATION URL with the appropriate Shoutrrr URL scheme is strongly recommended.
Use Watchtower’s CLI migration tool to help convert legacy email configurations to Shoutrrr URLs or use the Shoutrrr Playground to help convert configurations for other services to Shoutrrr URLs.
Overview
By default, Watchtower monitors all containers running on the Docker daemon it connects to (typically the local daemon, configurable via the --host flag).
To limit monitoring to specific containers, provide their names as arguments when starting Watchtower.
services:
watchtower:
command: nginx redis
image: nickfedor/watchtower:latest
volumes:
- /var/run/docker.sock:/var/run/docker.sock- In the above example, Watchtower monitors only the
nginxandrediscontainers, ignoring others.
To run a single update attempt and exit, use the run-once configuration option.
services:
watchtower:
command: nginx redis
environment:
WATCHTOWER_RUN_ONCE: true
image: nickfedor/watchtower:latest
volumes:
- /var/run/docker.sock:/var/run/docker.sock- This command triggers an update attempt for “nginx” and “redis” containers, displays debug output, and removes the Watchtower container upon completion.
General Options
Help
Displays documentation for supported flags.
Argument: --help
Environment Variable: N/A
Type: N/A
Default: N/AHealth Check
Returns a success exit code for Docker HEALTHCHECK, verifying another process is running in the container.
Argument: --health-check
Environment Variable: None
Type: N/A
Default: N/AHEALTHCHECK.
Do not use on the main command line.