By default, watchtower will monitor all containers running within the Docker daemon to which it is pointed (in most cases this will be the local Docker daemon, but you can override it with the `--host` option described in the next section). However, you can restrict watchtower to monitoring a subset of the running containers by specifying the container names as arguments when launching watchtower.
```
docker run -d \
--name watchtower \
-v /var/run/docker.sock:/var/run/docker.sock \
centurylink/watchtower nginx redis
```
In the example above, watchtower will only monitor the containers named "nginx" and "redis" for updates -- all of the other running containers will be ignored.
When no arguments are specified, watchtower will monitor all running containers.
### Options
### Options
Any of the options described below can be passed to the watchtower process by setting them after the image name in the `docker run` string:
Any of the options described below can be passed to the watchtower process by setting them after the image name in the `docker run` string:
@ -59,7 +74,6 @@ docker run --rm centurylink/watchtower --help
* `--debug` - Enable debug mode. When this option is specified you'll see more verbose logging in the watchtower log file.
* `--debug` - Enable debug mode. When this option is specified you'll see more verbose logging in the watchtower log file.
* `--help` - Show documentation about the supported flags.
* `--help` - Show documentation about the supported flags.
## Stopping Containers
## Stopping Containers
When watchtower detects that a running container needs to be updated it will stop the container by sending it a SIGTERM signal.
When watchtower detects that a running container needs to be updated it will stop the container by sending it a SIGTERM signal.