Self-host Lyrion Music Server with Levelrail
The successor to Logitech Media Server, streaming your music to Squeezebox players and apps.
- AuthorLMS-Community
- LicenceGPL-2.0-only
- Memory512 MiB
- Services1
How to self-host Lyrion Music Server
-
Pull the images
One image is pulled on your server.
Show images
lmscommunity/lyrionmusicserver:9.1.2
-
Create the app
One service starts in a single Compose app, with 3 named volume mounts for your data, on port 9000.
-
Fill in the secrets
2 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- Open the address, set the music folder to /music in the first run wizard.
Lyrion Music Server requirements
- Memory
- About 512 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 9000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-2.0-only, copyleft license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Lyrion Music Server. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Lyrion Music Server docs page.
Deploy Lyrion Music Server your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Lyrion Music Server from the CLI
levelrail-cli templates install lyrion --name my-lyrion Deploy Lyrion Music Server with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/lyrion/install \
-d '{
"name": "my-lyrion"
}' Lyrion Music Server configuration
Lyrion Music Server services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| lyrion | lmscommunity/lyrionmusicserver:9.1.2 | 9000 | config -> /configplaylists -> /playlistmusic -> /music |
Lyrion Music Server environment variables
| Variable | Service | Value |
|---|---|---|
| HTTP_PORT | lyrion | Preset by the template |
| TZ | lyrion | Preset by the template |
Ports and volumes
- Ports
- 9000
- Volumes
- 3 named mounts: config -> /config, playlists -> /playlist, music -> /music
Lyrion Music Server FAQ
How much memory does Lyrion Music Server need?
The catalog lists about 512 MiB of memory for Lyrion Music Server.
Does Lyrion Music Server run on arm64?
For Lyrion Music Server, arm64 support is not confirmed; amd64 is unknown.
What licence is Lyrion Music Server under?
Lyrion Music Server is licensed under GPL-2.0-only, which is copyleft, so changes you distribute must be shared under the same terms.
Does Lyrion Music Server need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Lyrion Music Server use?
Lyrion Music Server listens on port 9000 inside the stack.
Where does Lyrion Music Server keep its data?
In named volumes: config mounted at /config, playlists mounted at /playlist and music mounted at /music.
Can I deploy Lyrion Music Server on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Lyrion Music Server, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image lmscommunity/lyrionmusicserver:9.1.2 is what you deploy there.