For educational purposes only. This guide shows how to install self-hosted software on your own hardware. I don't condone piracy: only use these apps with media you own or have the right to use, and follow the law where you live. Back up your data first. Full disclaimer
Updated 8 November 2026 Tested with: TrueNAS 27.0.0-RC.1
Every guide on this site starts with a folder like /mnt/tank/configs/radarr. This post is where those folders come from. It walks through a TrueNAS storage setup for Docker apps in seven short steps: a pool, three datasets, the right permissions, snapshots and a backup.
It takes about 30 minutes, not counting the time a backup takes to copy.
On this page (13 sections)
- 1Plan your pool
- 2What you need for a TrueNAS storage setup
- 3Step 1: Choose a layout
- 4Step 2: Create the pool
- 5Step 3: Create the datasets
- 6Step 4: Set the permissions
- 7Step 5: Make a folder for each app
- 8Step 6: Turn on snapshots
- 9Step 7: Add a real backup
- 10Lessons from my own server
- 11Troubleshooting
- 12Useful commands
- 13Frequently asked questions
Plan your pool
The layout is the one choice that’s hard to change later, so try it here first. Pick your disks, then click one to break it. Under the planner is a generator that writes the folder commands for Step 5.
What you need for a TrueNAS storage setup
- TrueNAS installed, on its own small drive. TrueNAS keeps that drive to itself, so it can’t hold your files.
- At least one more disk for your data. Two or more if you want protection when a disk dies.
- Access to the TrueNAS web page, and its Shell (System → Shell) or SSH for Step 5.
The words you’ll see: a pool is a group of disks that acts as one big space. A dataset is like a folder inside it, but it can have its own permissions and snapshots. A snapshot is a saved moment you can go back to.
Step 1: Choose a layout
| Layout | Disks | Can lose | Good for |
|---|---|---|---|
| Mirror | 2 or more | All but one | Two disks, or a backup pool |
| RAIDZ1 | 3 or more | 1 | 3 to 5 disks, where you also keep a backup |
| RAIDZ2 | 4 or more | 2 | Bigger pools and big disks |
| Stripe | 1 or more | 0 | Only data you can easily replace |
I run RAIDZ1 on four 8 TB disks. That gives 21 TiB of usable space, and the pool keeps working if one disk dies.
Step 2: Create the pool
- Go to Storage → Create Pool.
- Give it a short lowercase name. I use
tank, and the rest of this guide does too. - Choose your layout and your disks, then check the summary before you confirm.
This wipes the disks you pick. Check each disk’s serial number against the sticker or your notes, as this is the step you can’t undo.
Step 3: Create the datasets
Go to Datasets, select your pool and press Add Dataset. Make these three, and choose Apps as the Dataset Preset for each:
| Dataset | Holds |
|---|---|
configs |
Each app’s settings and database, in its own folder |
stacks |
Your compose files |
media |
Downloads and your film and TV library |
Keep downloads and your library in the same dataset. Radarr and Sonarr use hardlinks to add a finished download to your library without copying it, and hardlinks can’t cross between datasets. Make them plain folders inside media, not datasets of their own.
If you’ll also share a dataset with Windows or Mac computers, look at the SMB or Multiprotocol presets for that one first.
Step 4: Set the permissions
On TrueNAS, apps run as the built-in apps user and group, number 568. So the rule is simple: root owns each dataset, the apps group can do everything, and nobody else gets in.
- In Datasets, select the dataset. On the Permissions card, press Edit.
- Set the owner to
rootand the group toapps. Tick Apply Owner and Apply Group. - Make sure the group has full control and “everyone” has nothing, then save.
- Do the same for the other two datasets.
These are new, empty datasets, so you don’t need to apply anything recursively. On a dataset that already has files, recursive changes reach every file at once. See the lessons below.
Step 5: Make a folder for each app
Use the generator above, or adapt this. Run it in the TrueNAS Shell or over SSH:
sudo mkdir -p /mnt/tank/configs/radarr
sudo chown root:apps /mnt/tank/configs/radarr
sudo chmod 770 /mnt/tank/configs/radarr
Then check that a container’s user can write there. You should see Permissions OK:
sudo setpriv --reuid=568 --regid=568 --clear-groups touch /mnt/tank/configs/radarr/write-test && echo "Permissions OK"
sudo rm -f /mnt/tank/configs/radarr/write-test
In your compose files, run each container as that user and point it at the folder:
environment:
- PUID=568
- PGID=568
volumes:
- /mnt/tank/configs/radarr:/config
- /mnt/tank/media:/data
Some images, such as many databases, insist on their own user. Treat those as one-offs and give that one folder to the user the image asks for.
Step 6: Turn on snapshots
- Go to Data Protection → Periodic Snapshot Tasks → Add.
- Choose
tank/configsand tick Recursive. - Set the Snapshot Lifetime to 1 week and the schedule to daily. Mine runs at 23:30.
- Save, then make a second task for
tank/stacks.
I don’t snapshot media. Arr apps replace files all the time, and a snapshot would hold on to the old copies and their space until it expires.
To get one file back, copy it out of the hidden snapshot folder:
ls /mnt/tank/configs/.zfs/snapshot/
To put a whole dataset back, use Rollback on its snapshot in TrueNAS. That throws away everything changed since the snapshot, so copy out a single file instead if you can.
Step 7: Add a real backup
Snapshots aren’t a backup. They live on the same disks, so they go if the pool goes. You need a copy somewhere else:
- A second pool in the same box covers a dead pool and your own mistakes. A mirror is a good choice. This is what I have.
- A second machine, or somewhere off-site, also covers fire, theft and a power surge. Data Protection → Replication Tasks can send your snapshots to another TrueNAS machine.
Mine runs from scripts at night: database dumps at 02:00, then a copy of configs and stacks to my backup pool at 04:00. My backup pool is in the same box, so an off-site copy is still on my list.
However you do it, restore a file from it once. Until you’ve done that, you don’t know it works.
Lessons from my own server
- One permissions call locked out 14,692 files. I sent TrueNAS’s permissions API a single new entry, and it replaced the whole list rather than adding to it. Downloads stopped about 12 hours later. If you change permissions by API or script, read the current list first and send the whole list back.
- Snapshot tasks can vanish. After I rebuilt my datasets, my tasks were gone, and I ran for about two weeks with no snapshots before I noticed. Check your tasks after any rebuild.
- Replication can fail quietly. When I recreated one app’s dataset, my whole nightly replication task failed for two nights with no alert. Look at each task’s state now and then, not just that it’s enabled.
- Disk letters change. A failing disk of mine went from
sdftosdbbetween reboots. Always go by serial number before you pull or wipe one.
Troubleshooting
| Problem | Try this |
|---|---|
| A container says “permission denied” | Run the write test in Step 5 on that folder, and check PUID and PGID are 568. Then look at the real permissions, not just ls: getfacl /mnt/tank/configs/radarr |
ls -l looks right, but it’s still denied |
TrueNAS uses NFSv4 ACLs, and they can override what ls shows. Check Permissions in Datasets |
| Radarr or Sonarr copy files instead of hardlinking | Downloads and library must be in one dataset, and mounted into the container as one path such as /data |
A folder of yours isn’t under /mnt |
Anything outside your pools can be lost in a TrueNAS update. Keep app data on a pool |
| The pool says DEGRADED | A disk has failed or dropped out. Note its serial number under Storage and replace it soon. Your data is still there |
Useful commands
# Pool health and space
zpool status
zpool list
# Space used by each dataset
zfs list -o name,used,avail,mountpoint
# Snapshots on a dataset
zfs list -t snapshot tank/configs
# Confirm the apps group number
getent group apps
I wrote this from my own server, on TrueNAS 27 RC.1, and checked the menu names against that version. I tested the folder commands and the write test on a real dataset. My pools were set up on an earlier version, so I haven’t clicked through Steps 2 and 3 on 27. Menu names can move between versions.
Frequently asked questions
Why does my container say permission denied on TrueNAS?
Check PUID and PGID are 568 (the apps group), then check the real permissions with getfacl. TrueNAS uses NFSv4 ACLs, which can override what ls -l shows.
Why do Radarr and Sonarr copy files instead of hardlinking?
Downloads and your library must be in one dataset and mounted into the container as one path, such as /data. Hardlinks can't cross datasets.
Are snapshots a backup?
No. Snapshots protect against deleted or changed files, but they live on the same pool. A real backup is a copy on another machine or disk, which Step 7 sets up.
Can I keep app data outside /mnt?
Don't. Anything outside your pools can be lost in a TrueNAS update. Keep app data on a pool.
What does DEGRADED mean on a pool?
A disk has failed or dropped out. Your data is still there. Note the disk's serial number under Storage and replace it soon.
Thank you
TrueNAS Community Edition is free thanks to iXsystems, and it’s built on OpenZFS, whose developers look after the part that keeps your data safe.
Related guides: TrueNAS 27 RC.1 · TrueNAS Home Assistant Card · Your First Docker App · Media Server Stack · Arr Stack
If this guide helped you, consider buying me a coffee. It helps keep guides like this one coming.
Get new guides by email
About one email a month: new step-by-step guides and card releases. No spam, unsubscribe any time.
