At least the volume mappings are looking good. App and database separated and on cache (ssd) storage.
Can you please report back if the next core update succeeds with this setup?
The problems you still have are pauses in playback right? I suspect you should investigate your network setup (outside the unraid server). Network setup is often the root cause of this sort of problems with playback. See the suggestions from the masters at https://help.roonlabs.com/portal/en/kb/articles/networking-best-practices . This forum also has many discussions on this topic.
Updated from the iPad, no issues. Server updated and is working properly. Added 16 Gb of Ram to 32.
No skipping and plays any format with ease. Thanks to all for the help with the configuration.
I have a Synology NAS that runs docker, and this presents a temptation to move my roon core onto it off of my mac. It’s all spinning disk; no cache, but it’s generally has about .5G of memory unused and plenty of CPU. Is this even close to being viable?
Based on subsequent events, this has to be more of ‘Roon for Android runs into network issues’ and nothing to do with Docker. All is well, docker-image-wise.
Do you have some feature on the wireless network that blocks broadcast over wifi? I had that issue with my Sonos as well, using Ubiquiti wifi products. The iPhone then could not find the Sonos.
I am assuming that the mac is using a wired connection. Otherwise, the above does not apply.
@Steef_de_Bruijn Steef I am not familiar with Linux, but I have installed your Docker file on a Synology NAS DSM 7 and mapped the drives. Roon has downloaded, but when I run the Docker my apps can’t see the Roon Core. I’m running Roon 1.8. Is there anything you can suggest - thanks (I am a real newbie sorry)
Nice how you use an alternate uid. I should do that sometime but I am afraid I run into file access problems on the music and backup shares.
Beware that you download the Roon software during image build. This is perfectly fine as long as you just distribute the docker file. You are not allowed to distribute a pre-built image this way per licensing restrictions from Roonlabs.
@Steef_de_Bruijn Hi, I manually re-created a new container and manually set up as host, it had defaulted to bridged. Everything is now working perfectly. Thank you for the advice and creating the Docker. Enjoying Roon on DSM 7 now.
Works well, that Dockerfile is really clean compared to what I had cooked up earlier.
I hope you don’t mind me copying a few lines
You might want to add the systemd service file as well. I’m not entirely sure it’s needed, but why not.
I shamelessly copied and briefly modified @Steef_de_Bruijn his container scripts into a docker container that runs in Home Assistant ;-).
Home Assistant has an add-on store where you can add the URL https://github.com/matthijsberg/HomeAssistant-Addons . This allows you to install the container with a click. Since HA offers persistent storage and links to back-up and media folder I changed the docker file and run scripts to work with the HA framework and use those folders.
new Roon user here. Since I read all the thread without finding this information, if some of you is interested I managed to have Steef’s image up and running in a docker compose environment on Ubuntu (without using the “host” network). Here is the stanza describing it:
Also, don’t forget to open your firewall (if you have one active):
sudo ufw allow from xxx.xxx.xxx.0/24 to xxx.xxx.xxx.xxx port 1900 proto udp
sudo ufw allow from xxx.xxx.xxx.0/24 to xxx.xxx.xxx.xxx port 9003 proto udp
sudo ufw allow from xxx.xxx.xxx.0/24 to xxx.xxx.xxx.xxx port 9100:9200 proto tcp
I’ll test it in the next days for full functionality, but I thought this could be of general interest.
Regards,
Antonello
P.S. - Funny enough, the same configuration on Windows Docker Desktop running on wsl fails to connect. The server is found, but the connection fails consistently. Not that important to me (I use it just for dev), but if someone has some suggestion I’d appreciate it.