· Can’t reach my Server, remotes or ARC
· Other ARC issues
· I'm trying to set-up again...after a l o n g break. I have ROONServer hosted on unRAID, and previously...I had the Docker set-up with a Music path of /mnt/user/share/folder; and things worked. I could see music, using the ROON app on my iPad.
· Nothing special here
Sorry; also…I’m sure I could map to the share/folder “directly” from the app. But shouldn’t the set-up above, basically “offer up” that folder to me?
Hi @Chris_Lehner1,
Thanks for the clarification.
To set expectations clearly: Roon does not support Docker-based, virtualized, or containerized deployments (including unRAID Docker setups). Because of this, we’re unfortunately not able to troubleshoot or validate behavior related to how storage paths are exposed inside a container.
Under the hood, Roon Server accesses network storage using standard file-sharing mechanisms (for example, CIFS/SMB). In a Docker or virtualized environment, how those paths are mapped, mounted, or presented to the container is entirely handled by the host system and Docker configuration, which is outside of what we can support or diagnose.
So to answer your question directly:
No — the Docker setup itself does not “offer up” that folder to Roon in a supported or guaranteed way. If things previously worked, that would have been incidental to the specific container and mount configuration at the time.
You’re welcome to inspect the Docker and host system logs on your side to investigate why the path is no longer behaving as expected, but from a support perspective, we can only assist with native, supported Roon Server installations.
Thanks for understanding.
I recommend creating a post in Tinkering, where the topic thread will remain open and not subject to topic timers. Some experienced Roon users have configured docker-based RoonServers in unofficial, but functioning, setups. They’d no doubt be willing to share some advice.
We’re going to allow this thread to auto-close due to inactivity after having received no responses in the last five days. You can reactivate the conversation by simply submitting a new tech support request here. The team will merge threads accordingly. Thank you!