Choosing Storage

NasDash must be able to write to the entire /app/data. The default Compose example uses a host folder. A named volume is optional.

Bind Mount (default)

Advantages: files are visible to host snapshots and folder backup tools. Existing installations already use ./data.

volumes:
  - ./data:/app/data

Prepare the directory before the first launch:

mkdir -p data/logos
sudo chown -R 1001:1001 data

The image process runs under UID/GID 1001:1001. A EACCES error, a false configuration success, or a restarting container may result from a non-writable directory.

Named Volume (optional)

Advantages: simple setup, no ownership conflicts with a host directory, stable name nasdash-data.

volumes:
  - nasdash-data:/app/data

Limitation: files are not directly visible in the Docker host's directory tree. Use a backup command via a temporary container. Do not use this on an existing ./data install unless you copy the files first.

Do Not Implicitly Switch Models

Switching from ./data to the nasdash-data volume without copying the data creates an apparently fresh instance. The old data has not disappeared, but it is no longer mounted.

Before migrating:

1. Stop NasDash;
2. Back up the complete source;
3. Copy all files, including hidden files and keys;
4. Set the owner to 1001:1001;
5. Start with the new target;
6. Verify connection, services, topology, logos, and integrations.