Self-host Emby with Levelrail
A media server that organizes your movies, shows, and music and streams them to any device.
- Memory1 GiB
- Archarm64
- Services1
How to self-host Emby
-
Pull the images
One image is pulled on your server.
Show images
lscr.io/linuxserver/emby:latest
-
Create the app
One service starts in a single Compose app, with 3 named volume mounts for your data, on port 8096.
-
Fill in the secrets
3 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.
Emby requirements
- Memory
- About 1 GiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8096
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- not yet recorded
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 8096 on the host, so open them in the VPS firewall only if you want that.
- Review. Image is not pinned to a version tag, so a redeploy can pull different code (lscr.io/linuxserver/emby:latest).
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Emby. 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 Emby docs page.
Deploy Emby your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Emby from the CLI
levelrail-cli templates deploy emby --name my-emby Deploy Emby with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/emby/deploy Emby configuration
Emby services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| emby | lscr.io/linuxserver/emby:latest | 8096 | emby_config -> /configemby_tvshows -> /tvshowsemby_movies -> /movies |
Emby environment variables
| Variable | Service | Value |
|---|---|---|
| PGID | emby | Preset by the template |
| PUID | emby | Preset by the template |
| TZ | emby | Preset by the template |
Ports and volumes
- Ports
- 8096
- Volumes
- 3 named mounts: emby_config -> /config, emby_tvshows -> /tvshows, emby_movies -> /movies
Emby FAQ
How much memory does Emby need?
The catalog lists about 1 GiB of memory for Emby.
Does Emby run on arm64?
For Emby, an arm64 image is published; amd64 is image published.
Does Emby need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Emby use?
Emby listens on port 8096 inside the stack.
Where does Emby keep its data?
In named volumes: emby_config mounted at /config, emby_tvshows mounted at /tvshows and emby_movies mounted at /movies.
Can I deploy Emby on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id emby for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image lscr.io/linuxserver/emby:latest is what you deploy there.