Self-host Ombi with Levelrail

A request portal where media server users ask for movies and shows and your download apps fill them. GPL-2.0 licensed. On first open, the wizard creates the admin account and connects your media server and Sonarr or Radarr.

  • AuthorOmbi-app
  • LicenceGPL-2.0
  • Memory384 MiB
  • Archarm64
  • Services1

How to self-host Ombi

  1. Pull the images

    One image is pulled on your server.

    Show images
    • lscr.io/linuxserver/ombi:4.53.10
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 3579.

  3. Fill in the secrets

    3 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Ombi requirements

Memory
About 384 MiB
Architectures
amd64 image published, arm64 image published
Ports
3579
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
GPL-2.0, 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 Ombi. 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 Ombi docs page.

Deploy Ombi your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Ombi from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain ombi=app.example.com.

levelrail-cli templates install ombi --name my-ombi

Deploy Ombi with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/ombi/install \
  -d '{
    "name": "my-ombi"
  }'

Ombi configuration

Ombi services

ServiceImagePortsVolumes
ombi lscr.io/linuxserver/ombi:4.53.10 3579 config -> /config

Ombi environment variables

VariableServiceValue
PGID ombi Preset by the template
PUID ombi Preset by the template
TZ ombi Preset by the template

Ports and volumes

Ports
3579
Volumes
1 named mount: config -> /config

Ombi FAQ

How much memory does Ombi need?

The catalog lists about 384 MiB of memory for Ombi.

Does Ombi run on arm64?

For Ombi, an arm64 image is published; amd64 is image published.

What licence is Ombi under?

Ombi is licensed under GPL-2.0, which is copyleft, so changes you distribute must be shared under the same terms.

Does Ombi need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Ombi use?

Ombi listens on port 3579 inside the stack.

Where does Ombi keep its data?

In a named volume: config mounted at /config.

Can I deploy Ombi 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 Ombi, 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 lscr.io/linuxserver/ombi:4.53.10 is what you deploy there.

levelrail-cli templates install ombi --name my-ombi