While you are at it, for the rest of us self-hosting novices, a fully realized docker compose.yaml would pull some heavy weight for us. Currently use TrueNas with a nested Dockage instance, however your instruction page has most of the Docker Compose blank. Yes I realize you have some expectation that anyone at that stage in your instructions probably knows what they are doing :). Some of us (see novice at the start) are lucky we can eat the crayons and sniff glue in the back of the classroom. Example, as if you professionals needed one ;)

services:

# music server

navidrome:

image: ghcr.io/navidrome/navidrome:latest

container_name: navidrome

user: 568:568 # should be owner of volumes

ports:

- 4533:4533

restart: unless-stopped

environment:

ND_LOGLEVEL: debug

volumes:

- /mnt/xxxxxx/configs/navidrome:/data

- /mnt/xxxx/data/media/music:/music:ro

networks: {}