Prowlarr is the indexer manager that pulls all your Usenet and torrent indexers into one place and automatically syncs them with Sonarr, Radarr, Lidarr, Readarr, and the rest of the *arr suite. Running it in a dedicated Proxmox LXC container on Ubuntu Server gives you clean isolation, easy resource control, and solid uptime without cluttering your host.
In this step-by-step tutorial you’ll create a lightweight Ubuntu LXC, install Docker inside it, deploy the official LinuxServer Prowlarr container, and complete the initial setup so your indexers are ready to feed your media automation stack.

What Is Prowlarr and Why Run It on Proxmox?
Prowlarr acts as a smart proxy and sync engine for indexers. Instead of adding the same tracker credentials to every *arr app, you configure them once in Prowlarr and it pushes the settings everywhere. It also handles search, RSS, and indexer health checks automatically.
A Proxmox LXC container is the perfect home: it’s lighter than a full VM, starts in seconds, and lets you snapshot or migrate the entire service without much hassle. Ubuntu Server provides a stable, well-supported base that plays nicely with Docker.
Prerequisites
Before you begin, make sure you have:
- A running Proxmox VE host (version 8.x recommended)
- Access to the Proxmox web UI and shell
- An Ubuntu 24.04 LTS template already downloaded in your CT Templates storage
- At least 2 CPU cores, 2 GB RAM, and 16 GB disk space available on the host
- Basic familiarity with Linux commands and Docker
Resource Recommendation:
| Component | Minimum | Recommended |
|---|---|---|
| CPU | 1 core | 2 cores |
| RAM | 1 GB | 2–4 GB |
| Storage | 8 GB | 16–32 GB (ZFS or LVM) |
Step 1: Create the Ubuntu Server LXC Container in Proxmox
- In the Proxmox web UI, right-click your node and choose Create CT.
- Select the Ubuntu 24.04 LTS template from your local storage.
- Set a hostname (e.g.,
prowlarr-lxc), a strong root password, and uncheck “Unprivileged container” only if you need full privileges (unprivileged + nesting is preferred). - Give the container 2 CPU cores and 2 GB RAM (you can adjust later).
- Create a root disk of at least 16 GB on your preferred storage.
- On the Network tab, assign a static IP on your bridge (vmbr0) and set the gateway.
- Finish the wizard and start the container.
- After the first boot, open the console and log in as root.
Enable nesting so Docker works smoothly inside the LXC:
pct set <CT-ID> -features nesting=1,keyctl=1
Replace <CT-ID> with your container’s numeric ID. Reboot the container once this is applied.
If you’re following our other Proxmox container tutorials, the steps here are identical to the ones used in our Dockge Proxmox installation.
Step 2: Update Ubuntu and Install Docker
SSH into the container (or use the Proxmox console) and run:
apt update && apt upgrade -y
apt install curl git -y
Now install Docker using the official convenience script (the same method used across our self-hosted guides):
curl -fsSL https://get.docker.com | sh
Verify Docker is running:
docker --version
docker run hello-world
Add your user to the docker group so you don’t need sudo for every command (optional but convenient):
usermod -aG docker $USER
newgrp docker
Step 3: Prepare Directories and Create docker-compose.yml
Create a dedicated folder for Prowlarr’s configuration:
mkdir -p /opt/prowlarr/config
chown -R 1000:1000 /opt/prowlarr
Create the compose file:
cd /opt/prowlarr
nano docker-compose.yml
Paste the following configuration (adjust TZ to your location — Asia/Kolkata works for most users in India):
version: '3.8'
services:
prowlarr:
image: lscr.io/linuxserver/prowlarr:latest
container_name: prowlarr
environment:
- PUID=1000
- PGID=1000
- TZ=Asia/Kolkata
volumes:
- /opt/prowlarr/config:/config
ports:
- 9696:9696
restart: unless-stopped
Save and exit (Ctrl+O, Enter, Ctrl+X in nano).
Step 4: Start Prowlarr
Launch the container:
docker compose up -d
Check the logs to confirm it started correctly:
docker compose logs -f prowlarr
You should see Prowlarr initializing its database and web server. Once the logs show “Application startup complete,” you’re ready to access the UI.
Step 5: Access the Web UI and Run Initial Setup
Open your browser and go to http://YOUR-LXC-IP:9696.
The first-time wizard will appear. Set a strong username and password and choose “Forms” authentication.
Head to Settings → General and enable API access (you’ll need the API key later for *arr apps).
Pro Tip: If the UI doesn’t load, double-check that port 9696 isn’t blocked by the host firewall and that the container has network access.
Step 6: Add Indexers and Sync with Your *arr Apps
In Prowlarr:
- Go to Indexers → Add Indexer and search for your favorite Usenet or torrent trackers.
- Configure each one with your credentials or API keys.
- Go to Apps and add Sonarr, Radarr, Lidarr, etc. Prowlarr will automatically push all configured indexers to them.
This one-time setup replaces manually configuring indexers in every app — the whole point of Prowlarr.
For detailed indexer recommendations and quality profiles, refer to the Prowlarr Servarr Wiki.
Troubleshooting Common Issues
- Container won’t start: Run
docker compose logs prowlarrand check for permission errors on the /config volume. - UI unreachable: Verify the port mapping and that the LXC firewall allows inbound traffic on 9696.
- Docker command not found: Make sure you’re in the docker group or use sudo.
- High CPU/memory: Increase container resources in Proxmox and restart the LXC.
Most issues trace back to missing nesting features or incorrect volume permissions — both easily fixed with the commands above.
Keeping Prowlarr Updated
Updates are simple with Docker:
cd /opt/prowlarr
docker compose pull
docker compose up -d
Prowlarr itself can also update from within the UI under System → Updates. The LinuxServer image stays current with the latest stable releases.
Security and Best Practices
- Run the container as a non-root user (PUID/PGID 1000 is standard).
- Expose Prowlarr only through a reverse proxy (Nginx Proxy Manager or Traefik) with HTTPS.
- Regularly snapshot the LXC in Proxmox before major updates.
- Backup the
/opt/prowlarr/configfolder — it contains your entire indexer database.
If you’re running multiple media automation tools, consider our Wallos Proxmox setup or Redlib Proxmox container guides for a complete stack.
Final Thoughts
You now have Prowlarr running cleanly inside a Proxmox LXC container on Ubuntu Server, ready to manage every indexer your *arr suite needs. The combination of Proxmox isolation and Docker simplicity gives you a maintainable, upgradable, and portable service that fits perfectly into any homelab.
Once your indexers are synced, head back to Sonarr or Radarr and watch the magic happen. If you run into any issues or want to add reverse-proxy, authentication, or monitoring, drop a comment below — happy to help.