Skip to content
Esc

Install Rerinku View

On this page

Check the platform, cameras and storage in Planning your installation, then choose an installation method below. If the console is already running, go straight to Quick start.

Release preparation: The Docker image rerinku/view is published and ready to use. The download URLs and file names of the Linux, macOS and Windows packages are still placeholders; check the release status on the download page. Until those packages are published, the download commands below do not work.

Install

Tarballs are provided for x86-64 and ARM64. Download and install (on ARM64 machines, replace amd64 with arm64):

curl -LO https://download.rerinku.com/onboard/rerinku-view_linux_amd64.tar.gz
tar -xzf rerinku-view_linux_amd64.tar.gz
sudo install -m 755 rerinkuview /usr/local/bin/

Run it in the foreground once first. Rerinku View creates the config file config.yaml and the data directory data/ in the current directory:

mkdir -p ~/rerinku && cd ~/rerinku
rerinkuview

Open http://<machine-ip>:8080 in a browser. If you see the console, it worked. Once you’ve confirmed everything is fine, press Ctrl+C to stop it, then set it up as a systemd service for long-term use:

sudo useradd -r -s /usr/sbin/nologin rerinku
sudo mkdir -p /var/lib/rerinku-view
sudo chown rerinku: /var/lib/rerinku-view
# /etc/systemd/system/rerinku-view.service
[Unit]
Description=Rerinku View
After=network-online.target
Wants=network-online.target

[Service]
User=rerinku
# The config file config.yaml and the data directory data/ both live here
WorkingDirectory=/var/lib/rerinku-view
Environment=RERINKU_BIN_DIR=/var/lib/rerinku-view/bin
ExecStart=/usr/local/bin/rerinkuview
Restart=on-failure
RestartSec=5

[Install]
WantedBy=multi-user.target
sudo systemctl daemon-reload
sudo systemctl enable --now rerinku-view

To connect USB cameras, or to use the GPU for hardware decoding in AI recognition, add the service user to the matching groups: sudo usermod -aG video,render rerinku, then restart the service.

Tarballs are provided for Apple silicon (arm64) and Intel (amd64). Download and extract (on Intel Macs, replace arm64 with amd64):

curl -LO https://download.rerinku.com/onboard/rerinku-view_darwin_arm64.tar.gz
tar -xzf rerinku-view_darwin_arm64.tar.gz

Gatekeeper blocks executables downloaded from a browser. Remove the quarantine flag first:

xattr -d com.apple.quarantine ./rerinkuview

Run it. Rerinku View creates config.yaml and data/ in the current directory:

mkdir -p ~/rerinku
cp ./rerinkuview ~/rerinku/
cd ~/rerinku
./rerinkuview

To start it automatically when the computer starts, write a launchd LaunchAgent (put it in ~/Library/LaunchAgents/, set WorkingDirectory to the directory above, and set RunAtLoad to true). USB cameras are not supported on macOS.

Zip packages are provided for x64 and ARM64. Download rerinku-view_windows_amd64.zip (on ARM64 machines, choose rerinku-view_windows_arm64.zip), extract it, and run it in PowerShell:

Expand-Archive rerinku-view_windows_amd64.zip -DestinationPath C:\rerinku-view
cd C:\rerinku-view
.\rerinkuview.exe

On first run, Windows Firewall shows a prompt. Allow access on Private networks, or devices on your LAN can’t connect. To start it with the system, use Task Scheduler (choose the At startup trigger and set Start in to C:\rerinku-view), or register it as a service with a tool such as NSSM. USB cameras are not supported on Windows.

The Docker image is published for both x86-64 (amd64) and ARM64; Docker pulls the one that matches your machine. It includes the AI recognition components and the decoding drivers for AMD GPUs; the Intel GPU drivers are in the x86-64 image only.

docker run -d --name rerinku-view \
  --network host \
  --restart unless-stopped \
  -v rerinku-view-data:/data \
  rerinku/view:latest

--network host is recommended: ONVIF auto-discovery relies on multicast, and WebRTC needs dynamic ports. Docker Desktop on macOS and Windows runs inside a virtual machine and can’t discover cameras automatically, so on those two platforms we recommend the native install.

For long-term use, we recommend Compose:

The Compose example below uses data/ under the current directory. On a new installation, create it and give the container user (UID 65532) write access first:

mkdir -p data
sudo chown 65532:65532 data
# compose.yaml
services:
  rerinku-view:
    image: rerinku/view:latest
    container_name: rerinku-view
    network_mode: host
    restart: unless-stopped
    volumes:
      - ./data:/data
    # Uncomment to use an Intel / AMD GPU for hardware decoding, or to connect a USB camera directly:
    # devices:
    #   - /dev/dri:/dev/dri
    #   - /dev/video0:/dev/video0
docker compose up -d

All of the image’s data lives in the /data volume. To upgrade, pull the new image and recreate the container: docker compose pull && docker compose up -d.

On first start, Rerinku View opens three ports to your LAN: 8080 for the console, 1883 for MQTT (used by devices to connect), and 5060 for GB28181 SIP. The GB28181 platform is on by default, and its registration password is change-me. If you don’t use GB28181, turn it off under Settings → GB28181. If you do, change the password first. See the Configuration reference.

Check that the service is running properly:

curl http://127.0.0.1:8080/healthz

After installation

Once the console opens and /healthz reports a healthy service, follow Quick start to connect your first camera and check recording. If startup fails or another machine cannot reach the console, see Troubleshooting.