Skip to content

Install on Synology NAS

ChannelWatch runs as a Docker container. These steps show how to run that container on Synology NAS. ChannelWatch does not have a native Synology package.

  • DSM 7.2 or newer is the easiest path because it includes Container Manager
  • A writable shared folder for ChannelWatch data, such as /volume1/docker/channelwatch
  • A reachable Channels DVR server on your LAN

If you want the simplest install path, start with the base Docker Compose guide. This page focuses on the Synology-specific UI and permission details.

Open Container Manager in DSM. If you do not see it yet, install it from Package Center first.

Create a project folder for ChannelWatch in a shared location, for example:

/volume1/docker/channelwatch

In Container Manager > Project, create a new project and paste the same compose file used in the Docker guide:

services:
channelwatch:
image: coderluii/channelwatch:latest
container_name: channelwatch
volumes:
- /volume1/docker/channelwatch:/config
environment:
TZ: "America/New_York"
PUID: "1026"
PGID: "100"
ports:
- "8501:8501"
restart: unless-stopped

Replace the timezone and volume path with values that match your NAS.

Synology often assigns user IDs that do not match the default Linux 1000:1000 pattern. Set PUID and PGID to the account that owns your ChannelWatch folder so the container can write settings.json, logs, and backups cleanly.

If you skip this step, the container may start but fail to write under /config.

The example uses bridge mode with an explicit mapping for port 8501. Use the DVR’s reachable LAN address in the setup wizard.

If your Synology model and DSM build allow host networking, you can replace the ports block with network_mode: host. That is the easier option for DVR auto-discovery.

After the project starts, open:

http://your-synology-ip:8501

Then follow First-Run Configuration to add your DVR, choose alert types, and set notification providers.

For a compatible release, use Settings > Updates inside ChannelWatch. See Updating ChannelWatch for supported source versions and the runtime limits.

If the release requires an image update, pull the image and recreate the project through Container Manager. A restart alone continues using the current container image. Keep the /config bind mount pointed at the same Synology folder so settings, logs, keys, and backups survive.