Installation¶
Choose the installation method that best fits your needs. Torrentarr offers multiple installation options for different environments and preferences.
Installation Methods¶
Docker (Recommended)¶
Docker provides the easiest and most consistent way to run Torrentarr across all platforms.
Best for:
- Users already running qBittorrent and Arr apps in Docker
- Simplified updates and maintenance
- Consistent environment across platforms
- Users who want easy path mapping
Get Started: Docker Installation Guide →
docker run -d \
--name torrentarr \
-p 6969:6969 \
-v /path/to/config:/config \
feramance/torrentarr:latest
Binary Download¶
Download pre-built executables for Linux, macOS, or Windows. Self-contained builds include the .NET runtime — no separate .NET install required.
Best for:
- Native installs without Docker
- Simple single-file deployment
- Systems where Docker isn't available
- Quick testing without building from source
Get Started: Binary Installation Guide →
# Linux/macOS (x64 example)
curl -L -o torrentarr https://github.com/Feramance/Torrentarr/releases/latest/download/torrentarr-linux-x64
chmod +x torrentarr
./torrentarr
Systemd Service¶
Run Torrentarr as a system service on Linux (typically with a binary under /usr/local/bin or similar).
Best for:
- Production deployments on Linux servers
- Automatic startup on boot
- Integration with system logging
- Resource management and monitoring
Get Started: Systemd Setup Guide →
From source¶
Build and run from the repository when you are developing or need an unpublished build.
Best for:
- Contributors and local development
- Testing changes before a release
Use a .NET SDK matching the repo (see repository global.json / CI), then:
See the Development Guide for the full workflow (restore, tests, publishing).
Comparison¶
| Feature | Docker | Binary | Systemd | From source |
|---|---|---|---|---|
| .NET SDK required | No | No | No | Yes |
| Easy updates | ✅ (docker pull) | ⚠️ Manual or WebUI binary update | ⚠️ Same as binary | Rebuild |
| Auto-start | ✅ | ⚠️ Manual | ✅ | ⚠️ Manual |
| Resource usage | Medium | Low | Low | Low |
| Isolation | ✅ | ❌ | ⚠️ Partial | ❌ |
| Path mapping | ✅ Easy | ⚠️ Manual | ⚠️ Manual | ⚠️ Manual |
| Multi-user | ✅ | ❌ | ✅ | ❌ |
Quick comparison¶
Choose Docker if:¶
- ✅ You're already using Docker for qBittorrent/Arr apps
- ✅ You want simple updates (just
docker pull) - ✅ You need consistent environments across systems
- ✅ You want easy path mapping and permission management
Choose Binary if:¶
- ✅ You want a native install without Docker
- ✅ You want a single downloadable executable
- ✅ You're testing Torrentarr quickly
- ✅ Docker isn't available
Choose Systemd if:¶
- ✅ You're on Linux and want system integration
- ✅ You need automatic startup on boot
- ✅ You want centralized logging via journald
- ✅ You're running a production server
Choose From source if:¶
- ✅ You are developing or patching Torrentarr
- ✅ You need a build that is not yet in releases
Prerequisites¶
Regardless of installation method, you'll need:
- qBittorrent - Running and accessible
- v4.x or v5.x supported
- WebUI enabled
-
Authentication configured
-
Arr Instance - At least one of:
- Radarr (v3.x, v4.x, v5.x)
- Sonarr (v3.x, v4.x)
-
Lidarr (v1.x, v2.x)
-
Network Access - Torrentarr needs to reach:
- qBittorrent WebUI
- Arr instance(s) API
- Internet (for auto-updates, optional)
After Installation¶
Once you've installed Torrentarr using your preferred method:
- First Run - Generate default configuration
-
Configure qBittorrent - Set connection details
-
Configure Arr Instances - Add your Radarr/Sonarr/Lidarr
-
Set Up Categories & Tags - Essential for tracking
-
Verify Operation - Check logs and WebUI
- WebUI Guide →
Migration¶
Already running Torrentarr and want to switch installation methods?
Getting Help¶
Need assistance with installation?
Next Steps¶
Ready to install? Choose your method:
- 🐳 Docker Installation → (Recommended)
- 📦 Binary Installation →
- ⚙️ Systemd Service →
Or jump straight to:
- 🚀 Quick Start Guide → - Get running in 5 minutes!