Watchtower

https://watchtower.nickfedor.com/latest/
Admin
Watchtower is a solution for automating Docker container image updates, keeping containers...
Tokens:21,457
Snippets:163
Trust Score:5.7
Update:11 months ago
Show doc for...
Tokens:
Raw
### Download Docker Compose file (curl)

Source: https://watchtower.nickfedor.com/latest/quickstart

This command uses `curl` to download the example `docker-compose.yaml` file for Watchtower. It saves the file to `docker-compose.yaml` in the current directory, allowing for easy setup with Docker Compose.

```bash
curl -L https://raw.githubusercontent.com/nicholas-fedor/watchtower/refs/heads/main/examples/default/docker-compose.yaml -o docker-compose.yaml
```

--------------------------------

### Download Docker Compose file (PowerShell)

Source: https://watchtower.nickfedor.com/latest/quickstart

This PowerShell command downloads the example `docker-compose.yaml` file for Watchtower from a GitHub repository. This file defines the Watchtower service for use with Docker Compose.

```powershell
iwr -Uri https://raw.githubusercontent.com/nicholas-fedor/watchtower/refs/heads/main/examples/default/docker-compose.yaml -OutFile docker-compose.yaml
```

--------------------------------

### Run Watchtower with Docker Compose

Source: https://watchtower.nickfedor.com/latest/quickstart

This command starts the Watchtower service defined in the `docker-compose.yaml` file in detached mode. It uses Docker Compose to manage the container lifecycle.

```bash
docker compose up -d
```

--------------------------------

### Watchtower HTTP API Configuration Examples (CLI)

Source: https://watchtower.nickfedor.com/latest/advanced-features/http-api

These examples demonstrate how to configure Watchtower's HTTP API port and host using command-line interface arguments. This allows customization of the listening address and port for the API server.

```bash
--http-api-port=8080
```

```bash
--http-api-host=127.0.0.1 --http-api-port=8080
```

```bash
--http-api-host=192.168.1.100 --http-api-port=9090
```

--------------------------------

### Signal URL Examples

Source: https://watchtower.nickfedor.com/latest/notifications/overview

These examples illustrate various ways to construct a Signal notification URL, including sending to single or multiple recipients, sending to groups, using authentication, and disabling TLS for local testing.

```url
signal://localhost:8080/+1234567890/+0987654321

```

```url
signal://localhost:8080/+1234567890/+0987654321/+1123456789/group.testgroup

```

```url
signal://localhost:8080/+1234567890/group.abcdefghijklmnop=

```

```url
signal://user:password@localhost:8080/+1234567890/+0987654321

```

```url
signal://localhost:8080/+1234567890/+0987654321?token=YOUR_API_TOKEN

```

```url
signal://localhost:8080/+1234567890/+0987654321?disabletls=yes

```

--------------------------------

### Pull Watchtower Container Image using Docker

Source: https://watchtower.nickfedor.com/latest/getting-started/installation

Pulls the latest Watchtower container image from either Docker Hub or GitHub Container Registry. This command requires Docker to be installed and configured on your system. No specific inputs are needed, and the output is the downloaded container image.

```docker
docker pull nickfedor/watchtower:latest
```

```docker
docker pull ghcr.io/nicholas-fedor/watchtower:latest
```

--------------------------------

### Watchtower Docker Compose configuration

Source: https://watchtower.nickfedor.com/latest/quickstart

This is the `docker-compose.yaml` file that defines the Watchtower service. It specifies the image to use, sets the restart policy, and mounts the Docker socket for container management.

```yaml
services:
  watchtower:
    image: nickfedor/watchtower:latest
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
```

--------------------------------

### Download and Extract Watchtower Binary using PowerShell

Source: https://watchtower.nickfedor.com/latest/getting-started/installation

Downloads the latest Watchtower binary for Windows (amd64) from GitHub Releases and extracts it to the current directory. This script requires PowerShell and the System.IO.Compression.FileSystem assembly. The output is the watchtower.exe file in the current directory.

```powershell
iwr (iwr https://api.github.com/repos/nicholas-fedor/watchtower/releases/latest | ConvertFrom-Json).assets.where({$_.name -like "*windows_amd64*.zip"}).browser_download_url -OutFile watchtower.zip; Add-Type -AssemblyName System.IO.Compression.FileSystem; $zip = [System.IO.Compression.ZipFile]::OpenRead("$PWD\watchtower.zip"); $zip.Entries | Where-Object {$_.Name -eq 'watchtower.exe'} | ForEach-Object {[System.IO.Compression.ZipFileExtensions]::ExtractToFile($_, "$PWD\watchtower.exe", $true)}; $zip.Dispose(); Remove-Item watchtower.zip; if (Test-Path ".\watchtower.exe") { Write-Host "Successfully installed watchtower.exe to current directory" } else { Write-Host "Failed to install watchtower.exe" }
```

--------------------------------

### Example Watchtower Notification Output

Source: https://watchtower.nickfedor.com/latest/notifications/templates

This snippet displays an example of Watchtower's notification output when a container is updated and an error log is present. It shows the summary of scanned, updated, and failed containers, along with specific details of the update and error messages.

```text
5 Scanned, 1 Updated, 0 Failed
- /container (repo/image:latest): abcdef12 updated to 34567890

Logs:
2025-08-20T06:00:13-07:00 [error] Operation failed. Try again later.
```

--------------------------------

### Run Watchtower with Docker CLI

Source: https://watchtower.nickfedor.com/latest/quickstart

This command pulls and runs the Watchtower container as a detached service. It mounts the Docker socket to allow Watchtower to interact with the Docker daemon. The container is configured to restart automatically unless explicitly stopped.

```bash
docker run -d \
  --name watchtower \
  --restart unless-stopped \
  -v /var/run/docker.sock:/var/run/docker.sock \
  nickfedor/watchtower
```

--------------------------------

### Download and Extract Watchtower Binary using Bash

Source: https://watchtower.nickfedor.com/latest/getting-started/installation

Downloads the latest Watchtower binary for Linux (amd64) or macOS (amd64) from GitHub Releases and extracts it to the current directory. This script requires curl and tar. The output is the watchtower executable in the current directory.

```bash
curl -L $(curl -s https://api.github.com/repos/nicholas-fedor/watchtower/releases/latest | grep -o 'https://[^\"]*linux_amd64[^\"]*\.tar\.gz') | tar -xz -C . watchtower && if [ -f ./watchtower ]; then echo "Successfully installed watchtower to current directory"; else echo "Failed to install watchtower"; fi
```

```bash
curl -L $(curl -s https://api.github.com/repos/nicholas-fedor/watchtower/releases/latest | grep -o 'https://[^\"]*darwin_amd64[^\"]*\.tar\.gz') | tar -xz -C . watchtower && if [ -f ./watchtower ]; then echo "Successfully installed watchtower to current directory"; else echo "Failed to install watchtower"; fi
```

--------------------------------

### Configure Lifecycle Hooks using Dockerfile Labels

Source: https://watchtower.nickfedor.com/latest/advanced-features/lifecycle-hooks

Example of specifying various lifecycle hook commands and UID/GID using LABEL instructions in a Dockerfile. These commands are executed by Watchtower at different stages of the container update process.

```dockerfile
LABEL com.centurylinklabs.watchtower.lifecycle.pre-check="/sync.sh"
LABEL com.centurylinklabs.watchtower.lifecycle.pre-update="/dump-data.sh"
LABEL com.centurylinklabs.watchtower.lifecycle.post-update="/restore-data.sh"
LABEL com.centurylinklabs.watchtower.lifecycle.post-check="/send-heartbeat.sh"
LABEL com.centurylinklabs.watchtower.lifecycle.uid="1000"
LABEL com.centurylinklabs.watchtower.lifecycle.gid="1000"
```

--------------------------------

### Configure Lifecycle Hooks using Docker Run Labels

Source: https://watchtower.nickfedor.com/latest/advanced-features/lifecycle-hooks

Example of specifying lifecycle hook commands and UID/GID using Docker container labels with the `docker run` command. These hooks allow custom actions before and after container updates.

```bash
docker run -d \
--label=com.centurylinklabs.watchtower.lifecycle.pre-check="/sync.sh" \
--label=com.centurylinklabs.watchtower.lifecycle.pre-update="/dump-data.sh" \
--label=com.centurylinklabs.watchtower.lifecycle.post-update="/restore-data.sh" \
--label=com.centurylinklabs.watchtower.lifecycle.post-check="/send-heartbeat.sh" \
--label=com.centurylinklabs.watchtower.lifecycle.uid="1000" \
--label=com.centurylinklabs.watchtower.lifecycle.gid="1000" \
someimage
```

--------------------------------

### Watchtower Slack Notification (Docker CLI)

Source: https://watchtower.nickfedor.com/latest/notifications/overview

Example of configuring Watchtower to send notifications to Slack using environment variables in a Docker run command.

```shell
docker run -d \
  --name watchtower \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -e WATCHTOWER_NOTIFICATIONS=slack \
  -e WATCHTOWER_NOTIFICATION_SLACK_HOOK_URL="https://hooks.slack.com/services/xxx/yyyyyyyyyyyyyyy" \
  -e WATCHTOWER_NOTIFICATION_SLACK_IDENTIFIER=watchtower-server-1 \
  -e WATCHTOWER_NOTIFICATION_SLACK_CHANNEL=#my-custom-channel \
  nickfedor/watchtower
```

--------------------------------

### Docker Compose - Scoping Watchtower Instances

Source: https://watchtower.nickfedor.com/latest/advanced-features/running-multiple-instances

This Docker Compose configuration demonstrates how to set up multiple Watchtower instances with different scopes. It includes examples of a scoped Watchtower instance managing scoped containers, and an unscoped Watchtower instance managing unscoped containers.

```yaml
version: '3' 

services:
  app-with-scope:
    image: myapps/monitored-by-watchtower
    labels: [ "com.centurylinklabs.watchtower.scope=myscope" ]

  scoped-watchtower:
    image: nickfedor/watchtower
    volumes: [ "/var/run/docker.sock:/var/run/docker.sock" ]
    command: --interval 30 --scope myscope
    labels: [ "com.centurylinklabs.watchtower.scope=myscope" ]

  unscoped-app-a:
    image: myapps/app-a

  unscoped-app-b:
    image: myapps/app-b
    labels: [ "com.centurylinklabs.watchtower.scope=none" ]

  unscoped-app-c:
    image: myapps/app-b
    labels: [ "com.centurylinklabs.watchtower.scope=" ]

  unscoped-watchtower:
    image: nickfedor/watchtower
    volumes: [ "/var/run/docker.sock:/var/run/docker.sock" ]
    command: --interval 30 --scope none

```

--------------------------------

### Watchtower Slack Notification (Docker Compose)

Source: https://watchtower.nickfedor.com/latest/notifications/overview

Example of configuring Watchtower to send notifications to Slack using environment variables in a Docker Compose file.

```yaml
services:
  watchtower:
    image: nickfedor/watchtower:latest
    environment:
      WATCHTOWER_NOTIFICATIONS: slack
      WATCHTOWER_NOTIFICATION_SLACK_HOOK_URL: "https://hooks.slack.com/services/xxx/yyyyyyyyyyyyyyy"
      WATCHTOWER_NOTIFICATION_SLACK_IDENTIFIER: watchtower-server-1
      WATCHTOWER_NOTIFICATION_SLACK_CHANNEL: "#my-custom-channel"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
```

--------------------------------

### Check Docker Version CLI

Source: https://watchtower.nickfedor.com/latest/getting-started/usage

Command to check the version of the Docker engine installed on the host system. This is recommended for compatibility with Watchtower.

```shell
docker version
```

--------------------------------

### Customizing Watchtower Notification Templates (Go Template)

Source: https://watchtower.nickfedor.com/latest/notifications/templates

This example illustrates the structure of a custom notification template for Watchtower, using Go's templating language. It covers conditional logic for reports, iterating over updated, fresh, skipped, and failed containers, and displaying log entries.

```gohtml
{{- if .Report -}}
  {{- with .Report -}}
{{len .Scanned}} Scanned, {{len .Updated}} Updated, {{len .Failed}} Failed
{{- if ( or .Updated .Failed ) -}}
      {{- range .Updated -}}
- {{.Name}} ({{.ImageName}}): {{.CurrentImageID.ShortID}} updated to {{.LatestImageID.ShortID}}
      {{- end -}}
      {{- range .Fresh -}}
- {{.Name}} ({{.ImageName}}): {{.State}}
      {{- end -}}
      {{- range .Skipped -}}
- {{.Name}} ({{.ImageName}}): {{.State}}: {{.Error}}
      {{- end -}}
      {{- range .Failed -}}
- {{.Name}} ({{.ImageName}}): {{.State}}: {{.Error}}
      {{- end -}}
{{- end -}}
  {{- end -}}
{{- if .Entries -}}

Logs:
{{- end -}}
{{range .Entries -}}{{.Time.Format "2006-01-02T15:04:05Z07:00"}} [{{.Level}}] {{.Message}}{{cdot "\n"}}{{- end -}}
```

--------------------------------

### Watchtower Shoutrrr Notification (Docker CLI)

Source: https://watchtower.nickfedor.com/latest/notifications/overview

Example of configuring Watchtower to use Shoutrrr notifications with a generated URL, replacing legacy email flags.

```shell
docker run -d \
  --name watchtower \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -e WATCHTOWER_NOTIFICATIONS=shoutrrr \
  -e WATCHTOWER_NOTIFICATION_URL=smtp://user@example.com:secret@smtp.example.com:587/?fromaddress=sender@example.com&toaddresses=recipient@example.com&encryption=ExplicitTLS&usestarttls=yes \
  -e WATCHTOWER_NOTIFICATION_EMAIL_DELAY=10 \
  -e WATCHTOWER_NOTIFICATION_EMAIL_SUBJECTTAG=Watchtower \
  nickfedor/watchtower
```

--------------------------------

### Watchtower HTTP API Update Trigger Examples (curl)

Source: https://watchtower.nickfedor.com/latest/advanced-features/http-api

These curl commands illustrate how to trigger container updates via the Watchtower HTTP API, including options for no image filtering, filtering by specific image tags, and filtering by image name without tags.

```bash
curl -H "Authorization: Bearer mytoken" localhost:8080/v1/update
```

```bash
curl -H "Authorization: Bearer mytoken" localhost:8080/v1/update?image=foo/bar:1.0,foo/baz:latest
```

```bash
curl -H "Authorization: Bearer mytoken" localhost:8080/v1/update?image=foo/bar,foo/baz
```

--------------------------------

### Watchtower Legacy Email Notification (Docker CLI)

Source: https://watchtower.nickfedor.com/latest/notifications/overview

Example of configuring Watchtower to use legacy email notifications via environment variables in a Docker run command.

```shell
docker run -d \
  --name watchtower \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -e WATCHTOWER_NOTIFICATIONS=email \
  -e WATCHTOWER_NOTIFICATION_EMAIL_SERVER=smtp.example.com \
  -e WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PORT=587 \
  -e WATCHTOWER_NOTIFICATION_EMAIL_SERVER_USER=user@example.com \
  -e WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PASSWORD=secret \
  -e WATCHTOWER_NOTIFICATION_EMAIL_FROM=sender@example.com \
  -e WATCHTOWER_NOTIFICATION_EMAIL_TO=recipient@example.com \
  nickfedor/watchtower
```

--------------------------------

### Watchtower Shoutrrr Notification (Docker Compose)

Source: https://watchtower.nickfedor.com/latest/notifications/overview

Example of configuring Watchtower to use Shoutrrr notifications with a generated URL, replacing legacy email flags in Docker Compose.

```yaml
services:
  watchtower:
    image: nickfedor/watchtower:latest
    environment:
      WATCHTOWER_NOTIFICATIONS: shoutrrr
      WATCHTOWER_NOTIFICATION_URL: smtp://user@example.com:secret@smtp.example.com:587/?fromaddress=sender@example.com&toaddresses=recipient@example.com&encryption=ExplicitTLS&usestarttls=yes
      WATCHTOWER_NOTIFICATION_EMAIL_DELAY: "10"
      WATCHTOWER_NOTIFICATION_EMAIL_SUBJECTTAG: Watchtower
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
```

--------------------------------

### Watchtower Legacy Email Notification (Docker Compose)

Source: https://watchtower.nickfedor.com/latest/notifications/overview

Example of configuring Watchtower to use legacy email notifications via environment variables in a Docker Compose file.

```yaml
services:
  watchtower:
    image: nickfedor/watchtower:latest
    environment:
      WATCHTOWER_NOTIFICATIONS: email
      WATCHTOWER_NOTIFICATION_EMAIL_SERVER: smtp.example.com
      WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PORT: 587
      WATCHTOWER_NOTIFICATION_EMAIL_SERVER_USER: user@example.com
      WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PASSWORD: secret
      WATCHTOWER_NOTIFICATION_EMAIL_FROM: sender@example.com
      WATCHTOWER_NOTIFICATION_EMAIL_TO: recipient@example.com
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
```

--------------------------------

### Docker Compose: Email Notification Setup

Source: https://watchtower.nickfedor.com/latest/notifications/overview

Sets up Watchtower email notifications within a Docker Compose environment. This method allows for defining the Watchtower service, its image, environment variables for email configuration, and volume mounts. It supports both authenticated SMTP and simple relay configurations.

```yaml
services:
  watchtower:
    image: nickfedor/watchtower:latest
    environment:
      WATCHTOWER_NOTIFICATIONS: email
      WATCHTOWER_NOTIFICATION_EMAIL_FROM: sender@example.com
      WATCHTOWER_NOTIFICATION_EMAIL_TO: recipient@example.com
      WATCHTOWER_NOTIFICATION_EMAIL_SERVER: smtp.example.com
      WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PORT: 587
      WATCHTOWER_NOTIFICATION_EMAIL_SERVER_USER: user
      WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PASSWORD: secret
      WATCHTOWER_NOTIFICATION_EMAIL_DELAY: 10
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
```

```yaml
services:
  watchtower:
    image: nickfedor/watchtower:latest
    environment:
      WATCHTOWER_NOTIFICATIONS: email
      WATCHTOWER_NOTIFICATION_EMAIL_FROM: sender@example.com
      WATCHTOWER_NOTIFICATION_EMAIL_TO: recipient@example.com
      WATCHTOWER_NOTIFICATION_EMAIL_SERVER: relay.example.com
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
```

--------------------------------

### Prometheus Scrape Configuration for Watchtower Metrics

Source: https://watchtower.nickfedor.com/latest/advanced-features/metrics

This configuration snippet defines how Prometheus can scrape metrics from Watchtower. It specifies the job name, scrape interval, the metrics endpoint, and authentication token. Ensure the target address and port match your Watchtower setup.

```yaml
scrape_configs:
  - job_name: watchtower
    scrape_interval: 5s
    metrics_path: /v1/metrics
    bearer_token: demotoken
    static_configs:
      - targets:
        - 'watchtower:8080'

```

--------------------------------

### Docker CLI: Email Notification Setup

Source: https://watchtower.nickfedor.com/latest/notifications/overview

Configures Watchtower to send email notifications using a specified SMTP server with authentication. Requires setting various environment variables for sender, recipient, server details, and credentials. The delay for sending notifications can also be configured.

```docker
docker run -d \
  --name watchtower \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -e WATCHTOWER_NOTIFICATIONS=email \
  -e WATCHTOWER_NOTIFICATION_EMAIL_FROM=sender@example.com \
  -e WATCHTOWER_NOTIFICATION_EMAIL_TO=recipient@example.com \
  -e WATCHTOWER_NOTIFICATION_EMAIL_SERVER=smtp.example.com \
  -e WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PORT=587 \
  -e WATCHTOWER_NOTIFICATION_EMAIL_SERVER_USER=user \
  -e WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PASSWORD=secret \
  -e WATCHTOWER_NOTIFICATION_EMAIL_DELAY=10 \
  nickfedor/watchtower
```

```docker
docker run -d \
  --name watchtower \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -e WATCHTOWER_NOTIFICATIONS=email \
  -e WATCHTOWER_NOTIFICATION_EMAIL_FROM=sender@example.com \
  -e WATCHTOWER_NOTIFICATION_EMAIL_TO=recipient@example.com \
  -e WATCHTOWER_NOTIFICATION_EMAIL_SERVER=relay.example.com \
  nickfedor/watchtower
```

--------------------------------

### Control CPU Settings Copying Mode for Podman

Source: https://watchtower.nickfedor.com/latest/configuration/arguments

Manages how CPU settings are copied when Watchtower recreates containers, specifically addressing differences between Docker and Podman regarding NanoCPUs. Options are 'auto', 'full', and 'none'. 'auto' detects Podman and filters NanoCPUs, 'full' copies all settings, and 'none' strips all CPU limits.

```bash
docker run -d \
    --name watchtower \
    -v /var/run/docker.sock:/var/run/docker.sock \
    nickfedor/watchtower \
    --cpu-copy-mode auto
```

```bash
docker run -d \
    --name watchtower \
    -v /var/run/docker.sock:/var/run/docker.sock \
    nickfedor/watchtower \
    --cpu-copy-mode full
```

```bash
docker run -d \
    --name watchtower \
    -v /var/run/docker.sock:/var/run/docker.sock \
    nickfedor/watchtower \
    --cpu-copy-mode none
```

--------------------------------

### Build Amazon ECR Credential Helper Dockerfile

Source: https://watchtower.nickfedor.com/latest/configuration/private-registries

This Dockerfile builds the amazon-ecr-credential-helper image. It sets up the Go environment, downloads the source code, builds the binary, and makes it available in the /go/bin directory.

```dockerfile
FROM golang:1.25

ENV GO111MODULE off
ENV CGO_ENABLED 0
ENV REPO github.com/awslabs/amazon-ecr-credential-helper/ecr-login/cli/docker-credential-ecr-login

RUN go get -u $REPO

RUN rm /go/bin/docker-credential-ecr-login

RUN go build \
 -o /go/bin/docker-credential-ecr-login \
 /go/src/$REPO

WORKDIR /go/bin/

```

--------------------------------

### Docker Commands for ECR Credential Helper

Source: https://watchtower.nickfedor.com/latest/configuration/private-registries

These Docker commands demonstrate how to create a volume, build the ECR credential helper image, and then run a container to copy the built helper binary into the created volume.

```bash
docker volume create helper

docker build -t aws-ecr-dock-cred-helper .

docker run  -d --rm --name aws-cred-helper \
  --volume helper:/go/bin aws-ecr-dock-cred-helper

```

--------------------------------

### Watchtower General Options (CLI Arguments)

Source: https://watchtower.nickfedor.com/latest/configuration/arguments

This section outlines common command-line arguments for Watchtower. It includes flags for displaying help, enabling debug and trace modes, setting log levels and formats, disabling ANSI colors, and triggering a one-time run.

```text
Argument: --help

```

```text
Argument: --debug, -d

```

```text
Argument: --trace

```

```text
Argument: --log-level
     Possible Values: panic, fatal, error, warn, info, debug, trace

```

```text
Argument: --log-format, -l
     Possible Values: Auto, LogFmt, Pretty, JSON

```

```text
Argument: --no-color

```

```text
Argument: --run-once, -R

```

--------------------------------

### Simple Template for Preview Tool

Source: https://watchtower.nickfedor.com/latest/notifications/templates

This Go template is adapted for use with the Watchtower Template Preview Tool, which uses a 'notifications.Data' struct with '.Entries' as the log list. It formats individual log entries in real-time.

```Go Template
{{- range $i, $e := .Entries -}}
{{- if $i}}{{- println -}}{{- end -}}
{{- $msg := $e.Message -}}
{{- if eq $msg "Found new image" -}}
    Found new image: {{$e.Data.image}} ({{with $e.Data.new_id}}{{.}}{{else}}unknown{{end}})
{{- else if eq $msg "Stopping container" -}}
    Stopped stale container: {{$e.Data.container}} ({{with $e.Data.id}}{{.}}{{else}}unknown{{end}})
{{- else if eq $msg "Started new container" -}}
    Started new container: {{$e.Data.container}} ({{with $e.Data.new_id}}{{.}}{{else}}unknown{{end}})
{{- else if eq $msg "Removing image" -}}
    Removed stale image: {{with $e.Data.image_id}}{{.}}{{else}}unknown{{end}}
{{- else if $e.Data -}}
    {{$msg}} | {{range $k, $v := $e.Data -}}{{$k}}={{$v}} {{- end}}
{{- else -}}
    {{$msg}}
{{- end -}}
{{- end -}}

```

--------------------------------

### Enable Separate Notifications Per Container (Docker Compose)

Source: https://watchtower.nickfedor.com/latest/notifications/overview

An example of how to enable separate notifications for each updated container using Docker Compose. This involves setting the `WATCHTOWER_NOTIFICATIONS` and `WATCHTOWER_NOTIFICATION_SPLIT_BY_CONTAINER` environment variables.

```yaml
docker run -d \
  --name watchtower \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -e WATCHTOWER_NOTIFICATIONS=slack \
  -e WATCHTOWER_NOTIFICATION_SLACK_HOOK_URL="https://hooks.slack.com/services/xxx/yyyyyyyyyyyyyyy" \
  -e WATCHTOWER_NOTIFICATION_SPLIT_BY_CONTAINER=true \
  nickfedor/watchtower

```

--------------------------------

### Configure HTTP Proxy for Registry Connections

Source: https://watchtower.nickfedor.com/latest/configuration/arguments

Sets up an HTTP proxy for Watchtower to use when connecting to Docker registries. This is configured via the HTTP_PROXY or http_proxy environment variable. The value should be a string representing the proxy URL, including the port. This is useful in environments with restricted network access.

```bash
docker run -e HTTP_PROXY="http://proxy.example.com:3128" ...
```

--------------------------------

### Access Container Metadata in Lifecycle Hooks

Source: https://watchtower.nickfedor.com/latest/advanced-features/lifecycle-hooks

Example shell script demonstrating how to access container metadata, such as the container name, using the `WT_CONTAINER` environment variable, which is provided as a JSON object. This is useful for custom logic within hook scripts.

```bash
#!/bin/sh
# Parse container name from WT_CONTAINER
CONTAINER_NAME=$(echo $WT_CONTAINER | jq -r '.name')

# Use Synology API to stop container properly
synowebapi --exec api=SYNO.Docker.Container method="stop" name="$CONTAINER_NAME"
```

--------------------------------

### Gotify Configuration Options

Source: https://watchtower.nickfedor.com/latest/notifications/overview

Parameters for Gotify notifications, including the Gotify instance URL, app token, and the option to skip TLS certificate verification.

```Shell
Argument: --notification-gotify-url
Environment Variable: WATCHTOWER_NOTIFICATION_GOTIFY_URL
                Type: String
             Default: None
```

```Shell
Argument: --notification-gotify-token
Environment Variable: WATCHTOWER_NOTIFICATION_GOTIFY_TOKEN
                Type: String
             Default: None
```

```Shell
Argument: --notification-gotify-tls-skip-verify
Environment Variable: WATCHTOWER_NOTIFICATION_GOTIFY_TLS_SKIP_VERIFY
                Type: Boolean
             Default: false
```

--------------------------------

### Configure HTTPS Proxy for Registry Connections

Source: https://watchtower.nickfedor.com/latest/configuration/arguments

Sets up an HTTPS proxy for Watchtower to use when connecting to Docker registries. This is configured via the HTTPS_PROXY or https_proxy environment variable. The value should be a string representing the proxy URL, including the port. This is useful for secure registry connections through a proxy.

```bash
docker run -e HTTPS_PROXY="http://proxy.example.com:3128" ...
```

--------------------------------

### Watchtower Docker Compose Configuration

Source: https://watchtower.nickfedor.com/latest/advanced-features/http-api

This Docker Compose configuration sets up Watchtower to run with its HTTP API enabled for updates and metrics. It also shows how to configure a monitored application and exposes the necessary Docker socket and ports.

```yaml
services:
  app-monitored-by-watchtower:
    image: myapps/monitored-by-watchtower
    labels:
      - "com.centurylinklabs.watchtower.enable=true"

  watchtower:
    image: nickfedor/watchtower
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    command: --http-api-update --http-api-metrics
    environment:
      - WATCHTOWER_HTTP_API_TOKEN=mytoken
    labels:
      - "com.centurylinklabs.watchtower.enable=false"
    ports:
      - 8080:8080
    restart: unless-stopped
```

--------------------------------

### Run Watchtower with config.json

Source: https://watchtower.nickfedor.com/latest/configuration/private-registries

This Docker command demonstrates how to run Watchtower and mount a custom configuration file for private registry access. The `-v` flag maps the local `config.json` to the container's `/config.json` path.

```bash
docker run [...] -v <PATH>/config.json:/config.json nickfedor/watchtower
```

--------------------------------

### Run Watchtower Once for Specific Containers (Docker CLI)

Source: https://watchtower.nickfedor.com/latest/configuration/arguments

This command executes Watchtower to perform a single update attempt for the 'nginx' and 'redis' containers and then exits. The `--rm` option ensures the container is removed upon completion, and `--run-once` triggers the single update cycle. Debug output is displayed.

```docker
docker run --rm \
    -v /var/run/docker.sock:/var/run/docker.sock \
    nickfedor/watchtower \
    --run-once \
    nginx redis

```

--------------------------------

### Run Watchtower with Docker CLI

Source: https://watchtower.nickfedor.com/latest/notifications/templates

This snippet shows how to run Watchtower as a Docker container using the Docker CLI. It mounts the Docker socket, sets notification reporting and templating options, and specifies the Watchtower image.

```bash
docker run -d \
  --name watchtower \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -e WATCHTOWER_NOTIFICATION_REPORT="true" \
  -e WATCHTOWER_NOTIFICATION_TEMPLATE="{{- if .Report -}}\n  {{- with .Report -}}\n{{len .Scanned}} Scanned, {{len .Updated}} Updated, {{len .Failed}} Failed
{{- if ( or .Updated .Failed ) -}}\n      {{- range .Updated -}}
- {{.Name}} ({{.ImageName}}): {{.CurrentImageID.ShortID}} updated to {{.LatestImageID.ShortID}}
      {{- end -}}
      {{- range .Fresh -}}
- {{.Name}} ({{.ImageName}}): {{.State}}
      {{- end -}}
      {{- range .Skipped -}}
- {{.Name}} ({{.ImageName}}): {{.State}}: {{.Error}}
      {{- end -}}
      {{- range .Failed -}}
- {{.Name}} ({{.ImageName}}): {{.State}}: {{.Error}}
      {{- end -}}
{{- end -}}
  {{- end -}}
{{- if .Entries -}}\n
Logs:
{{- end -}}
{{range .Entries -}}{{.Time.Format "2006-01-02T15:04:05Z07:00"}} [{{.Level}}] {{.Message}}{{cdot "\n"}}{{- end -}}"
  watchtower-image
```

--------------------------------

### Default Simple Template for Log Entries

Source: https://watchtower.nickfedor.com/latest/notifications/templates

This Go template formats individual log entries as they occur when the '--notification-report' flag is not set. It processes 'info'-level log entries in real-time and formats key update events in past tense, including container and image details.

```Go Template
{{- range $i, $e := . -}}
{{- if $i}}{{- println -}}{{- end -}}
{{- $msg := $e.Message -}}
{{- if eq $msg "Found new image" -}}
    Found new image: {{$e.Data.image}} ({{with $e.Data.new_id}}{{.}}{{else}}unknown{{end}})
{{- else if eq $msg "Stopping container" -}}
    Stopped stale container: {{$e.Data.container}} ({{with $e.Data.id}}{{.}}{{else}}unknown{{end}})
{{- else if eq $msg "Started new container" -}}
    Started new container: {{$e.Data.container}} ({{with $e.Data.new_id}}{{.}}{{else}}unknown{{end}})
{{- else if eq $msg "Removing image" -}}
    Removed stale image: {{with $e.Data.image_id}}{{.}}{{else}}unknown{{end}}
{{- else if $e.Data -}}
    {{$msg}} | {{range $k, $v := $e.Data -}}{{$k}}={{$v}} {{- end}}
{{- else -}}
    {{$msg}}
{{- end -}}
{{- end -}}

```

--------------------------------

### Gotify Notifications - Docker CLI

Source: https://watchtower.nickfedor.com/latest/notifications/overview

Run Watchtower using Docker CLI to send notifications to a Gotify instance. This requires specifying the Gotify URL, app token, and optionally skipping TLS verification.

```docker
docker run -d \
  --name watchtower \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -e WATCHTOWER_NOTIFICATIONS=gotify \
  -e WATCHTOWER_NOTIFICATION_GOTIFY_URL="https://my.gotify.tld/" \
  -e WATCHTOWER_NOTIFICATION_GOTIFY_TOKEN="SuperSecretToken" \
  -e WATCHTOWER_NOTIFICATION_GOTIFY_TLS_SKIP_VERIFY=true \
  nickfedor/watchtower
```

--------------------------------

### Workaround for Multiple Notification Services (Environment Variable)

Source: https://watchtower.nickfedor.com/latest/notifications/overview

Demonstrates a workaround for a Viper bug that prevents comma-separated slices in environment variables for multiple notification services. This method uses quotes and replaces commas with spaces.

```shell
WATCHTOWER_NOTIFICATIONS="slack msteams"

```

--------------------------------

### Configure Watchtower with Docker Compose

Source: https://watchtower.nickfedor.com/latest/notifications/templates

This snippet demonstrates how to configure Watchtower using a Docker Compose file. It specifies the image, mounts the Docker socket, and sets environment variables for notification reporting, URL, and custom templates.

```yaml
services:
  watchtower:
    image: watchtower-image
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      WATCHTOWER_NOTIFICATION_REPORT: "true"
      WATCHTOWER_NOTIFICATION_URL: >
        discord://token@channel
        slack://watchtower@token-a/token-b/token-c
      WATCHTOWER_NOTIFICATION_TEMPLATE: |
        {{- if .Report -}}
          {{- with .Report -}}
        {{len .Scanned}} Scanned, {{len .Updated}} Updated, {{len .Failed}} Failed
        {{- if ( or .Updated .Failed ) -}}
            {{- range .Updated -}}
        - {{.Name}} ({{.ImageName}}): {{.CurrentImageID.ShortID}} updated to {{.LatestImageID.ShortID}}
            {{- end -}}
            {{- range .Fresh -}}
        - {{.Name}} ({{.ImageName}}): {{.State}}
            {{- end -}}
            {{- range .Skipped -}}
        - {{.Name}} ({{.ImageName}}): {{.State}}: {{.Error}}
            {{- end -}}
            {{- range .Failed -}}
        - {{.Name}} ({{.ImageName}}): {{.State}}: {{.Error}}
            {{- end -}}
        {{- end -}}
          {{- end -}}
        {{- if .Entries -}}

        Logs:
        {{- end -}}
        {{range .Entries -}}{{.Time.Format "2006-01-02T15:04:05Z07:00"}} [{{.Level}}] {{.Message}}{{cdot "\n"}}{{- end -}}
```

--------------------------------

### Go Template for Watchtower Report Display

Source: https://watchtower.nickfedor.com/latest/notifications/template-preview

This Go template displays a detailed report of container scans and updates. It conditionally shows scanned, updated, and failed counts, and iterates through different report categories like updated, fresh, skipped, and failed containers. It also handles cases where no report data is available by displaying log entries.

```go-template
{{- if .Report -}} {{- with .Report -}} {{len .Scanned}} Scanned, {{len .Updated}} Updated, {{len .Failed}} Failed {{- if ( or .Updated .Failed ) -}} {{- range .Updated}} - {{.Name}} ({{.ImageName}}): {{.CurrentImageID.ShortID}} updated to {{.LatestImageID.ShortID}} {{- end -}} {{- range .Fresh}} - {{.Name}} ({{.ImageName}}): {{.State}} {{- end -}} {{- range .Skipped}} - {{.Name}} ({{.ImageName}}): {{.State}}: {{.Error}} {{- end -}} {{- range .Failed}} - {{.Name}} ({{.ImageName}}): {{.State}}: {{.Error}} {{- end -}} {{- end -}} {{- end -}} {{- else -}} {{range .Entries -}}{{.Message}}{{"
"}}{{- end -}} {{- end -}}
```

--------------------------------

### Run Watchtower with Private Registry Credentials

Source: https://watchtower.nickfedor.com/latest/getting-started/usage

Command to run Watchtower with environment variables for private registry authentication (username and password). It also mounts the Docker socket and passes a debug flag.

```shell
docker run -d \
  --name watchtower \
  -e REPO_USER=username \
  -e REPO_PASS=password \
  -v /var/run/docker.sock:/var/run/docker.sock \
  --restart unless-stopped \
  nickfedor/watchtower container_to_watch --debug
```

--------------------------------

### Gotify Notifications - Docker Compose

Source: https://watchtower.nickfedor.com/latest/notifications/overview

Configure Watchtower in Docker Compose for Gotify notifications. This includes setting the Gotify URL, token, and TLS skip verify option via environment variables.

```yaml
services:
  watchtower:
    image: nickfedor/watchtower:latest
    environment:
      WATCHTOWER_NOTIFICATIONS: gotify
      WATCHTOWER_NOTIFICATION_GOTIFY_URL: "https://my.gotify.tld/"
      WATCHTOWER_NOTIFICATION_GOTIFY_TOKEN: "SuperSecretToken"
      WATCHTOWER_NOTIFICATION_GOTIFY_TLS_SKIP_VERIFY: true
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
```

--------------------------------

### Run Watchtower with Docker Hub Credentials (2FA)

Source: https://watchtower.nickfedor.com/latest/getting-started/usage

Command to run Watchtower when Docker Hub 2FA is enabled. It mounts the Docker config file (containing credentials from 'docker login') into the container.

```shell
docker run -d \
  --name watchtower \
  -v $HOME/.docker/config.json:/config.json \
  -v /var/run/docker.sock:/var/run/docker.sock \
  --restart unless-stopped \
  nickfedor/watchtower container_to_watch --debug
```

--------------------------------

### Default Report Template for Session Summaries

Source: https://watchtower.nickfedor.com/latest/notifications/templates

This Go template generates a summary of container statuses (scanned, updated, failed, etc.) followed by logs when the '--notification-report' flag is set. It's suitable for aggregated notifications like email or Slack messages.

```Go Template
{{- if .Report -}}
  {{- with .Report -}}
    {{len .Scanned}} Scanned, {{len .Updated}} Updated, {{len .Failed}} Failed
    {{- if ( or .Updated .Failed ) -}}
      {{- range .Updated}}
- {{.Name}} ({{.ImageName}}): {{.CurrentImageID.ShortID}} updated to {{.LatestImageID.ShortID}}
      {{- end -}}
      {{- range .Fresh}}
- {{.Name}} ({{.ImageName}}): {{.State}}
      {{- end -}}
      {{- range .Skipped}}
- {{.Name}} ({{.ImageName}}): {{.State}}: {{.Error}}
      {{- end -}}
      {{- range .Failed}}
- {{.Name}} ({{.ImageName}}): {{.State}}: {{.Error}}
      {{- end -}}
    {{- end -}}
  {{- end -}}
{{- if .Entries -}}

Logs:
{{- end -}}
{{range .Entries -}}{{.Time.Format "2006-01-02T15:04:05Z07:00"}} [{{.Level}}] {{.Message}}{{"\n"}}{{- end -}}


```

--------------------------------

### Set Minimum TLS Version for Registry Connections

Source: https://watchtower.nickfedor.com/latest/configuration/arguments

Configures the minimum TLS version allowed for connections to Docker registries. This overrides the default of TLS 1.2. Possible values include TLS1.0, TLS1.1, TLS1.2, and TLS1.3. Using older TLS versions is not recommended due to security risks.

```bash
docker run ... --registry-tls-min-version TLS1.3
```

--------------------------------

### Run Watchtower with TLS Verification (Docker CLI)

Source: https://watchtower.nickfedor.com/latest/configuration/secure-connections

This command runs Watchtower in detached mode, mounts the Docker TLS certificates, and enables TLS verification for secure connections to a remote Docker host. It requires the `DOCKER_CERT_PATH` environment variable to be set correctly on the host machine.

```bash
docker run -d \
--name watchtower \
-e DOCKER_HOST=$DOCKER_HOST \
-e DOCKER_CERT_PATH=/etc/ssl/docker \
-v $DOCKER_CERT_PATH:/etc/ssl/docker \
--restart unless-stopped
nickfedor/watchtower --tlsverify
```

--------------------------------

### Watchtower Secrets Usage (Docker Compose)

Source: https://watchtower.nickfedor.com/latest/configuration/arguments

This Docker Compose configuration demonstrates how to securely provide secrets to Watchtower. It defines a secret 'access_token' from a file and mounts it into the Watchtower service, referencing its path in the `WATCHTOWER_HTTP_API_TOKEN` environment variable.

```yaml
secrets:
  access_token:
    file: access_token

services:
  watchtower:
    secrets:
      - access_token
    environment:
      - WATCHTOWER_HTTP_API_TOKEN=/run/secrets/access_token

```

--------------------------------

### Convert Legacy Email to Shoutrrr URL with Watchtower CLI

Source: https://watchtower.nickfedor.com/latest/notifications/overview

Uses the `watchtower notify-upgrade` command to convert legacy email notification flags into a Shoutrrr URL. The output can be copied using `docker cp`.

```shell
docker cp <CONTAINER>:<FILE_PATH> ./watchtower-notifications.env
```

```shell
docker compose exec watchtower watchtower notify-upgrade
```

--------------------------------

### Configure No Proxy Domains

Source: https://watchtower.nickfedor.com/latest/configuration/arguments

Specifies a list of hosts or domains that should bypass the configured proxy when Watchtower connects to registries. This is configured via the NO_PROXY or no_proxy environment variable as a comma-separated string. It's useful for accessing local or internal resources directly.

```bash
docker run -e NO_PROXY="localhost,127.0.0.1,internal.example.com" ...
```

--------------------------------

### Include Specific Containers with Watchtower (Dockerfile)

Source: https://watchtower.nickfedor.com/latest/configuration/container-selection

This Dockerfile snippet shows how to enable Watchtower to monitor a container by setting the 'com.centurylinklabs.watchtower.enable' label to 'true'. This is used in conjunction with the '--label-enable' flag or 'WATCHTOWER_LABEL_ENABLE' environment variable.

```dockerfile
LABEL com.centurylinklabs.watchtower.enable="true"
```

--------------------------------

### Configure Watchtower Docker Compose for Signal Notifications

Source: https://watchtower.nickfedor.com/latest/notifications/overview

This snippet defines a Docker Compose service for Watchtower, specifying the image, environment variables for the Signal notification URL, and volume mounts for the Docker socket. This allows for declarative management of Watchtower with Signal integration.

```yaml
services:
  watchtower:
    image: nickfedor/watchtower:latest
    environment:
      WATCHTOWER_NOTIFICATION_URL: signal://localhost:8080/+1234567890/+0987654321
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock

```

--------------------------------

### Docker Compose for Watchtower and Private Registry

Source: https://watchtower.nickfedor.com/latest/getting-started/usage

A docker-compose.yml file to set up a service to be watched and the Watchtower container. It includes mounting the Docker socket and config.json, and customizes the Watchtower update interval.

```yaml
version: "3" 
services:
  cavo:
    image: ghcr.io/<org>/<image>:<tag>
    ports:
      - "443:3443"
      - "80:3080"
  watchtower:
    image: nickfedor/watchtower
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /root/.docker/config.json:/config.json
    command: --interval 30

```

--------------------------------

### Include Specific Containers with Watchtower (docker run)

Source: https://watchtower.nickfedor.com/latest/configuration/container-selection

This command demonstrates how to run a container that Watchtower should specifically monitor and update by setting the 'com.centurylinklabs.watchtower.enable' label to 'true'. This is used with the '--label-enable' flag on Watchtower.

```bash
docker run -d --label=com.centurylinklabs.watchtower.enable=true someimage
```

--------------------------------

### HTTP API Metrics Endpoint

Source: https://watchtower.nickfedor.com/latest/advanced-features/http-api

Exposes Prometheus-compatible metrics for monitoring and alerting.

```APIDOC
## GET /v1/metrics

### Description
This endpoint exposes Prometheus-compatible metrics for monitoring Watchtower's status and performance.

### Method
GET

### Endpoint
`/v1/metrics`

### Parameters
None

### Request Example
```bash
curl localhost:8080/v1/metrics
```

### Response
#### Success Response (200)
Prometheus-formatted metrics.

#### Response Example
```text
# HELP watchtower_container_scans_total Total number of containers scanned by Watchtower.
# TYPE watchtower_container_scans_total counter
watchtower_container_scans_total 15
# HELP watchtower_container_updates_total Total number of containers successfully updated by Watchtower.
# TYPE watchtower_container_updates_total counter
watchtower_container_updates_total 5
# HELP watchtower_last_scan_timestamp Timestamp of the last container scan.
# TYPE watchtower_last_scan_timestamp gauge
watchtower_last_scan_timestamp 1678886400
```
```

--------------------------------

### Testing Shoutrrr Notifications via CLI

Source: https://watchtower.nickfedor.com/latest/notifications/overview

This command-line instruction demonstrates how to test your configured Shoutrrr notification URL. It uses the `shoutrrr send` command with the `-u` flag for the URL and `-m` for the message content.

```shell
shoutrrr send -u <URL> -m "Test message"
```

--------------------------------

### Set Watchtower Stop Signal via Docker Run Command

Source: https://watchtower.nickfedor.com/latest/advanced-features/stop-signals

This snippet shows how to specify a custom stop signal for Watchtower directly on the command line when running a container. The `--label` flag is used with `docker run` to set the `com.centurylinklabs.watchtower.stop-signal` metadata. This allows for dynamic configuration of the stop signal without modifying the Dockerfile.

```bash
docker run -d --label=com.centurylinklabs.watchtower.stop-signal=SIGHUP someimage

```

--------------------------------

### Specify Docker Daemon Host Connection

Source: https://watchtower.nickfedor.com/latest/configuration/arguments

Configures the Docker daemon socket that Watchtower should connect to. This supports local Unix sockets or remote TCP connections. The default is `unix:///var/run/docker.sock`. For remote connections, use the format `tcp://hostname:port`.

```bash
docker run ... --host tcp://192.168.1.100:2376
```

--------------------------------

### Shoutrrr SMTP URL for Generic SSL Configuration

Source: https://watchtower.nickfedor.com/latest/notifications/overview

This snippet demonstrates the Shoutrrr SMTP URL for generic email servers using SSL (ImplicitTLS). It requires user credentials, sender, and recipient details, specifying port 465 for SSL connections and disabling STARTTLS. A timeout can be included.

```URL
smtp://${USER}:${PASSWORD}@smtp.example.com:465/?fromaddress=${FROM}&toaddresses=${TO}&encryption=ImplicitTLS&usestarttls=no&timeout=30s
```

--------------------------------

### Generate Base64 Auth String

Source: https://watchtower.nickfedor.com/latest/configuration/private-registries

This command generates a base64 encoded string for authentication, typically used in private registry configurations. It takes the format 'username:password' and pipes it to the base64 encoder. The `-w0` flag ensures no line wrapping.

```bash
echo -n 'username:password' | base64
```

```bash
echo -n "_json_key:$(cat gcloudauth.json)" | base64 -w0
```

--------------------------------

### List Docker Containers

Source: https://watchtower.nickfedor.com/latest/getting-started/overview

This command lists all currently running Docker containers. It displays the container ID, image used, status, exposed ports, and container name. This is useful for verifying container status and identifying which containers are running.

```bash
docker ps
```

--------------------------------

### Docker Compose for Watchtower with ECR Helper

Source: https://watchtower.nickfedor.com/latest/configuration/private-registries

This Docker Compose configuration sets up Watchtower to monitor and restart containers. It mounts the Docker socket, the ECR config, and the ECR helper binary volume, along with setting necessary environment variables for AWS.

```yaml
services:
 # Check for new images and restart things if a new image exists
 # for any of our containers.
 watchtower:
   image: nickfedor/watchtower:latest
   volumes:
     - /var/run/docker.sock:/var/run/docker.sock
     - .docker/config.json:/config.json
     - helper:/go/bin
   environment:
     - HOME=/
     - PATH=$PATH:/go/bin
     - AWS_REGION=us-west-1
volumes:
 helper:
   external: true

```
Tokens:
Raw