Installing Issuarr on Unraid

Issuarr has an Unraid template in this repository, templates/issuarr.xml. It runs the ghcr.io/issuarr/issuarr:latest image with the usual Unraid defaults (user 99, group 100, appdata under /mnt/user/appdata).

There are two ways to install it. Both use the same template and give you the same container.

Option 1: Community Applications

1. Open the Apps tab and search for Issuarr.
2. Click Install.
3. Fill in the paths (see below) and click Apply.
4. Open the web UI from the container's icon, or at http://<your-server>:8090, and follow Getting started.

Option 2: Add the template by hand

This works on any Unraid server, whether or not Community Applications is installed.

1. Open a terminal on the server (>_ in the top-right of the web UI) and download the template into your user templates folder:

   wget -O /boot/config/plugins/dockerMan/templates-user/my-issuarr.xml \
     https://raw.githubusercontent.com/issuarr/issuarr/main/templates/issuarr.xml
   

2. Go to Docker > Add Container and choose issuarr from the Template list.

3. Fill in the paths (see below) and click Apply.

4. Open the web UI from the container's icon, or at http://<your-server>:8090, and follow Getting started.

Paths and settings

Unraid sets the container's time zone (TZ) from Settings > Date and Time on its own.

Where to keep Appdata

Issuarr's database is fastest on a local filesystem, where it can use SQLite's WAL mode. Unraid's /mnt/user paths normally go through its FUSE layer (shfs), where WAL isn't safe, so Issuarr falls back to the slower rollback journal there. Both work; WAL just means fewer "database is locked" waits.

To get WAL, point Appdata at a pool or disk path instead, such as /mnt/cache/appdata/issuarr (use your pool's name if it isn't cache). If your appdata share is set to Exclusive access (Unraid 6.12 and later), /mnt/user/appdata skips FUSE and is fine as it is.

The log tells you which mode Issuarr picked at startup ([DB] Journal mode ...). More on this in Database is locked.

Coming from Mylar3 on Unraid

Your Mylar3 settings and database carry over. Either way below, keep the Comics and Downloads paths at the same container paths as before, because Mylar stored full paths in its database.

• Switch the existing container: stop it, click its icon, choose Edit, change Repository to ghcr.io/issuarr/issuarr:latest and click Apply. Optionally rename it to issuarr.
• Use the Issuarr template: stop the Mylar3 container, add Issuarr as above and set Appdata to your old Mylar3 folder (for example /mnt/user/appdata/mylar3), with the same Comics and Downloads mappings. Remove the Mylar3 container once Issuarr is working.

See Moving from Mylar3 to Issuarr for what to check afterwards.

Updates

The template follows the latest tag, which is rebuilt whenever a new Issuarr release lands on the main branch. Unraid shows update ready on the Docker tab when a new image is out; click it to update.

To try changes before they are released, change Repository to ghcr.io/issuarr/issuarr:dev and click Apply. The dev tag is rebuilt whenever Issuarr's dev branch changes, so it is less tested than latest. Change it back to latest to return to releases; your settings and library are kept either way.