Self-host Jackett with Levelrail
A proxy that translates queries from your media apps into torrent tracker searches.
- AuthorJackett
- LicenceGPL-2.0
- Memory256 MiB
- Archarm64
- Services1
How to self-host Jackett
-
Pull the images
One image is pulled on your server.
Show images
lscr.io/linuxserver/jackett:0.24.2663
-
Create the app
One service starts in a single Compose app, with 2 named volume mounts for your data, on port 9117.
-
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.
Jackett requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 9117
- 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.
- Host ports. It publishes port 9117 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Jackett. 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 Jackett docs page.
Deploy Jackett your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Jackett from the CLI
levelrail-cli templates deploy jackett --name my-jackett Deploy Jackett with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/jackett/deploy Jackett configuration
Jackett services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| jackett | lscr.io/linuxserver/jackett:0.24.2663 | 9117 | jackett_config -> /configjackett_downloads -> /downloads |
Jackett environment variables
| Variable | Service | Value |
|---|---|---|
| PGID | jackett | Preset by the template |
| PUID | jackett | Preset by the template |
| TZ | jackett | Preset by the template |
Ports and volumes
- Ports
- 9117
- Volumes
- 2 named mounts: jackett_config -> /config, jackett_downloads -> /downloads
Jackett FAQ
How much memory does Jackett need?
The catalog lists about 256 MiB of memory for Jackett.
Does Jackett run on arm64?
For Jackett, an arm64 image is published; amd64 is image published.
What licence is Jackett under?
Jackett is licensed under GPL-2.0, which is copyleft, so changes you distribute must be shared under the same terms.
Does Jackett need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Jackett use?
Jackett listens on port 9117 inside the stack.
Where does Jackett keep its data?
In named volumes: jackett_config mounted at /config and jackett_downloads mounted at /downloads.
Can I deploy Jackett 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 Jackett, 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/jackett:0.24.2663 is what you deploy there.