Choosing Storage
Named volume, bind mount, and UID/GID 1001:1001 permissions.
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/dataPrepare the directory before the first launch:
# Fresh empty directory; default container UID:GID
mkdir -p data
sudo chown 1001:1001 data
sudo chmod 700 dataThe default image uses UID:GID 1001:1001; an explicit Compose user overrides it. For existing files or Synology ACLs, stop NasDash, back up first and grant the actual runtime identity access to all data and logos. Do not apply recursive ownership changes blindly. See installation and permission diagnostics.
Named Volume (optional)
For a fresh installation, use the complete docker-compose.named-volume.yml from the product checkout. Its top-level declaration explicitly names the volume nasdash-data. Keep using that file for lifecycle commands. Runtime ownership and permissions still matter, especially with a custom UID:GID.
docker compose -f docker-compose.named-volume.yml up -d
docker compose -f docker-compose.named-volume.yml ps
docker compose -f docker-compose.named-volume.yml stop nasdashLimitation: 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:
- Stop NasDash.
- Back up the complete source.
- Copy every file, including keys and hidden files.
- Grant the actual runtime UID:GID access.
- Start with the new target.
- Verify login, services, topology, logos and integrations.