Cannot create Docker container on QNAP TBS-453A NAS (ref#G59M2M)

Support
1

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· I have a QNAP TBS-453A NAS and I am trying to set up the docker version of the server. I have installed conatainer, copied the YAML, valdiated it, when I press create I ge the message: "Make sure you configure all the necessary settings first."

Tell us about your home network

· Fritzbox 7590

2

Then, by all means, please give the application a name (red border because there is an issue) that meets the requirements (click the question mark to learn more about naming requirements).

3

Hello @martingh

The error “Make sure you configure all the necessary settings first” is caused by the Application name format. As indicated by the red border around the “Application name” field in your screenshot, QNAP Container Station requires this field to use only lowercase letters.

Change the Application name from RoonServer to roonserver and click Create.

4

Thanks! I did not notice the red border. The error message is perhaps a little cryptic. Anyway, I have now entered a correct name, so let’s see if it all works…

5

I am attempting to restore from backup. I selected the directory, but there was no list of backups to chose from. I pressed the button and the process seemed to start. The jelly-fish has been showing for over 90 mins. I have 11k tracks. Is this OK? Is there any way to monitor the progress, or stop it of it is not running correctly?

6

hallo @vadim ,

Thanks for your help. I have got a little further but I am still having problems getting the Docker version to restore a backup. I see you have had a similar discussion regarding a synology migration. I have posted screen shots under another ticket (ref#MR6I11).

I have copied the backup file into the Docker folder, and it gets found. But the folders are not available for the backup.

Please can you let me know explicitly how I can configure the docker version to find my local files when restoring the back-up. I can reindex them, in the docker version, but I am wanting a migration not a new install.

Thanks!

7

Hey @martingh,

Thanks for the update and additional information! When restoring a Roon backup within a Docker environment, the most common hurdle is the discrepancy between the host machine’s physical file paths and the “virtual” paths visible to Roon inside the container.

To ensure the Docker version can explicitly find and use your local files for a successful migration, follow these troubleshooting steps:

  1. Verify Volume Mappings: Roon inside Docker can only “see” folders that have been explicitly mapped in your container settings (Docker Compose or Synology Container Manager).

If you have copied your backup into the Docker folder, you must ensure that folder is mapped to a specific path inside the container. A typical configuration looks like this:

  • Host Path: /volume1/docker/roon/backups (The actual folder on your NAS)
  • Container Path: /backups (The path Roon sees)
When you go to Restore > Browse, you should look for the root folder /backups, not the long host path.
  1. Permissions and “System Internal User”: If the backup is visible but the folders within it are inaccessible, it is often a permission mismatch. On Synology, the Docker container often runs as a specific user.
  • Go to your NAS File Station.
  • Right-click the folder containing your backups and select Settings > Permissions.
  • Ensure that the user running the Docker container (often a specific UID like 1026 or the "System Internal User" for Container Manager) has Read & Write access to both the backup folder and the music folder.
Let me know if either help, thank you!
8

Hi @martingh,

We see a QNAP Roon Server instance associated with your account was active since you last posted. I’m assuming that you’ve set up a Docker at this point if you’re able to run the most recent build?

Please ping us here if you require additional assistance. This thread will auto-close eventually without any new responses from the OP. Thank you!