---
title: ATF Ruling 2016-1 Compliant Backups to Unraid
url: https://www.fastbound.com/faq/atf-ruling-2016-1-compliant-backups-to-unraid/
description: "Note: FastBound doesn’t have an Unraid device in-house to test against, so we can’t officially support this configuration. That said, customers have confirmed they’ve successfully installed and run this image on Unraid. The steps below reflect the standard Docker workflow and what those customers have reported. Create the two host folders first. Open the Unraid… Continue reading ATF Ruling 2016-1 Compliant Backups to Unraid"
---

Note: FastBound doesn’t have an Unraid device in-house to test against, so we can’t officially support this configuration. That said, customers have confirmed they’ve successfully installed and run this image on Unraid. The steps below reflect the standard Docker workflow and what those customers have reported.

Create the two host folders first. Open the Unraid web UI → Shares, and make sure you have a place for both volumes. A typical setup:

Config: /mnt/user/appdata/ffl-bound-book-backup

Data (where the bound book backups land): /mnt/user/fastbound-backup (create a new share for this, or use an existing one)

Go to the Docker tab. If Docker isn’t enabled, go to Settings → Docker, set Enable Docker to Yes, and apply.

Add the container. On the Docker tab, scroll to the bottom and click Add Container.

Fill in the template fields:

Name: ffl-bound-book-backup

Repository: fastbound/ffl-bound-book-backup:latest

Network Type: leave as bridge (no ports are needed — this is a backup tool, not a web service)

Add the /config volume. Click Add another Path, Port, Variable… and set:

Config Type: Path

Name: config

Container Path: /config

Host Path: /mnt/user/appdata/ffl-bound-book-backup

Access Mode: Read/Write

Add the /data volume. Click Add another Path… again:

Config Type: Path

Name: data

Container Path: /data

Host Path: /mnt/user/fastbound-backup

Access Mode: Read/Write

Click Apply. Unraid pulls the image and starts the container. On this first run it generates a sample accounts.json in your config folder and then stops itself. This stopping is expected behavior, not an error.

Edit accounts.json. Open the file at /mnt/user/appdata/ffl-bound-book-backup/accounts.json (via the Unraid file browser, a terminal, or an SMB share). Replace the sample values with your real FastBound account credentials/API details.

Start the container again. Back on the Docker tab, click the container icon → Start. It will now read your config and back up your bound book(s) to the /data folder.

A few notes: you’ll get your API key, audit token, and account number from inside your FastBound account (under Settings) to populate accounts.json — the image’s own README/sample file shows the exact field names. Since there’s no web port, you won’t have a UI to open; check the container’s Logs in Unraid to confirm backups are running. If you want it to run on a schedule, use Unraid’s User Scripts plugin to start the container periodically, or set a restart policy, since the image runs its backup job and exits rather than staying resident.