Docker reference
For your first installation, use the installation guides or Mac guide.
Media folder mappings
Each media line maps an existing folder on your computer to a folder below /media in Norri. Keep the final :ro to mount it read-only. A source can be on another disk; mount NAS shares on the Docker host first. Docker Desktop must have permission to access the selected folders.
To add another source, duplicate a media line and give it an existing host path and a unique destination, such as /media/KidsMovies. You can add several libraries of the same type. Select these /media/... paths in the Norri setup wizard.
Short Docker volume syntax can create an empty host folder if the source does not exist. Check the source path if a library appears empty. On Linux, PUID and PGID must identify an account that can read the source files and their parent folders. IDs 0 and 999 are not supported. Leave the Compose user setting unset.
NAS and container managers
In a Compose or Stack editor, paste the complete configuration, make the labeled changes, and deploy it.
For a manager’s individual fields, use image registry.norri.tv/norri/norri:latest, TCP port 11423:11423, the two writable data volumes, each separate read-only media folder, and the environment and startup settings in that file. Configure the GPU in your manager’s device settings.
Updates and backups
norri_postgres contains the database; norri_data contains application state. Keep both volumes and your Compose file or customized Docker run command. Media stays in its separate read-only host mounts.
The latest tag follows the recommended public release: the public beta now, then stable releases when available. Running containers stay on their installed version until you update them. Numbered tags remain available if you want to pin a particular release.
Before updating, stop the container with docker stop norri and back up both named volumes using your host’s backup tools. Keep a separate backup of your original media. The commands below use the default container name; substitute yours if you changed it.
Docker Compose
In the folder containing compose.yaml, run:
docker compose pull
docker compose up -d
Your saved folders, GPU settings, and data volumes are reused.
Docker run
Keep your saved, customized docker run command ready. If you did not save it, note your existing folder, GPU, and user-ID settings before removing the container, then prepare the matching Docker run example.
Pull the current image, then remove the stopped container:
docker pull --platform linux/amd64 registry.norri.tv/norri/norri:latest
docker rm norri
Run your saved command again to create the replacement. Keep the same two named data volumes and media folders. Removing the container does not delete these volumes.
After updating
Check your libraries and playback. A rollback may require restoring the matching earlier data backup as well as selecting an earlier versioned image.
Caution
Keep your persistent data
Do not use docker compose down -v for an update or troubleshooting: it deletes the persistent volumes. Ordinary docker compose down preserves them.
Another installation on the same host
For another installation on the same host, change the top-level Compose name, container_name, the published port, and both explicit volume names. A new folder alone does not isolate the fixed names in this example.
Server address and custom ports
Norri uses TCP port 11423 for its browser interface, setup wizard, and API. There is no separate administration port.
To use host port 12080, change the port mapping to "12080:11423", run docker compose up -d, and open http://YOUR_SERVER_IP:12080. Keep the container port at 11423. In Settings → General → Network, set Host port to 12080 and choose Save host port.
The setting records the address used for device links; it does not change Docker’s mapping. Update bookmarks, client addresses, and reverse-proxy upstreams that use the old port. See Server Configuration and Remote Access.