Watchtower Docker on QNAP NAS — Container Station Setup Guide

Why Run Watchtower on QNAP?

QNAP NAS units running Container Station are common homelab Docker hosts for Nextcloud, Jellyfin, Immich, Home Assistant, and Portainer. Without watchtower docker qnap set up, keeping those images current means logging into Container Station (or SSH) and manually pulling and recreating every container whenever a new tag ships.

Installing docker watchtower qnap automates that loop. If anything doesn't behave the way this guide describes, the Watchtower troubleshooting guide covers the errors people hit most often.

Prerequisites

• QNAP NAS running QTS 5.x or QuTS hero
• Container Station 3 installed from App Center
• Admin access to the QNAP web interface
• SSH enabled (Control Panel → Network & File Services → Telnet / SSH) — only needed for Method 1

Method 1: SSH + Docker Compose (Recommended)

SSH into the NAS and deploy Watchtower the same way you would on any Linux Docker host — Container Station 3 picks up and lists containers created this way automatically:

# SSH into the QNAP
ssh admin@192.168.1.x

# Create a working directory
mkdir -p /share/Container/watchtower
cd /share/Container/watchtower

# Create docker-compose.yml
cat > docker-compose.yml <<'EOF'
services:
  watchtower:
    image: containrrr/watchtower
    container_name: watchtower
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /etc/localtime:/etc/localtime:ro
    environment:
      - WATCHTOWER_CLEANUP=true
      - WATCHTOWER_POLL_INTERVAL=21600
EOF

# Start it
docker-compose up -d

For the full cron-vs-interval breakdown and timezone handling, see Watchtower Docker schedule configuration.

Method 2: Container Station "Create Application" (No SSH)

Container Station 3's Applications feature accepts a Docker Compose YAML directly and validates it before deploying — useful if you'd rather not enable SSH at all:

1. Open Container Station from the QNAP desktop
2. Go to Applications → Create
3. Choose Create Application and switch to the YAML editor
4. Paste the compose block from Method 1 above
5. Click Validate to catch formatting errors, then Create
6. For a full list of settings, see the Watchtower environment variables reference and add extra environment lines as needed

Common QNAP Watchtower Issues

Issue: "Permission denied" on /var/run/docker.sock

Make sure you're running the docker-compose command as admin or with sudo — QNAP's shell account permissions on the Docker socket depend on the account's group membership.

Issue: Container Station shows Watchtower as "Unhealthy"

Watchtower ships without a Docker health-check endpoint, so Container Station's health indicator is cosmetic here. Check docker logs watchtower to confirm it's actually polling and updating.

Issue: duplicate-looking containers after mixing Method 1 and Method 2

Only run Watchtower once per host. If you deployed it via SSH and then again through Create Application (or vice versa), remove one — two Watchtower instances watching the same Docker socket will both try to update the same containers. If you deliberately need more than one, see running multiple Watchtower instances safely.

Recommended QNAP Configuration

services:
  watchtower:
    image: containrrr/watchtower
    container_name: watchtower
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /etc/localtime:/etc/localtime:ro
    environment:
      - WATCHTOWER_CLEANUP=true
      - WATCHTOWER_SCHEDULE=0 0 3 * * *    # 3 AM daily
      - WATCHTOWER_NOTIFICATIONS=slack
      - WATCHTOWER_NOTIFICATION_SLACK_HOOK_URL=https://hooks.slack.com/...

For Discord, Telegram, email, and ntfy setup instead of Slack, see the Watchtower notifications guide.