Skip to content

Docker & Compose

If you already run a homelab, the container is the quickest way in. The image is multi-arch (amd64 + arm64) and published on GHCR.

ghcr.io/redth/remaestro:beta

Create compose.yaml:

services:
remaestro:
image: ghcr.io/redth/remaestro:beta
container_name: remaestro
restart: unless-stopped
# Host networking lets the hub discover and reach AV gear on your LAN (mDNS/SSDP/broadcast).
network_mode: host
volumes:
# The databases live under /app/data in the container — mount it or you lose everything
# the moment the container is recreated.
- ./data:/app/data
# Optional: let the supervisor manage container self-updates.
# - /var/run/docker.sock:/var/run/docker.sock

Then:

Terminal window
docker compose up -d
docker compose logs -f
  1. Start it with docker compose up -d.
  2. Open the console at http://<host-ip>:5006. The container listens on 5006 and, with host networking, that is the host’s port too — the appliance’s plain http://remaestro.local comes from the Pi image binding 80, which the container deliberately doesn’t do.
  3. Continue to First boot.

The container updates on the app cadence via the signed manifest at releases.remaestro.app/beta.json, which pins the image by digest. See Updating.