Download Mimir Server

# pull the published multi-architecture image, nothing to build
docker pull ghcr.io/marleshi/mimir:latest

# start it, with recordings and working space on folders you choose
docker run -d \
  --name mimir \
  --restart unless-stopped \
  --stop-timeout 120 \
  -p 8094:8093 \
  -e TZ=Australia/Perth \
  -e TRANSCODE_TEMP_DIR=/transcode \
  -v mimir-config:/config \
  -v /path/to/recordings:/recordings \
  -v /path/to/transcode:/transcode \
  ghcr.io/marleshi/mimir:latest

# follow the log while it starts
docker logs -f mimir

# then open the setup wizard at http://localhost:8094/

docker ps
curl http://localhost:8094/api/health

# add this line to the docker run command from the first block
-v /path/to/lineup:/lineup-input:ro

Add that line to expose a folder of M3U playlists and XMLTV guides. The folder then appears as lineup-input in the file picker, so you choose your files without typing paths, and Mimir re-reads them on every refresh — a regenerated playlist or guide is picked up automatically. Mount as many folders as you like, each under its own name.

# pull the new image, stop and remove the old container, then re-run
# the docker run command from the first block. The mimir-config
# volume keeps your settings, sources and recordings intact.
docker pull ghcr.io/marleshi/mimir:latest
docker stop mimir
docker rm mimir

Application state is kept in a named volume, while recordings and working space live in folders you choose, so pulling a new image never puts your library at risk. Point /transcode at a drive with room to spare: a recording is written there in full before it is finalised, about 5 GB per hour of HD. Keeping it on the same drive as your recordings makes that final step a move rather than a copy. The --stop-timeout 120 flag gives an in-progress recording up to two minutes to finalise before the container exits, so stopping or updating Mimir never cuts a capture short.

Set TZ to your own timezone, because recordings are scheduled in the container's clock, so leaving it wrong shifts every timer. On Windows and macOS, use Windows- or macOS-style paths for the two folders. On Linux or a NAS, add -e PUID=$(id -u) -e PGID=$(id -g) so the server runs as your user — it defaults to UID/GID 1000, and your recordings folder must be writable by whichever user you choose. Publishing the port with -p 8094:8093 works everywhere. On Linux or a NAS you can swap it for --network host instead, which lets the TV apps discover the server automatically; the web interface then answers on port 8093.