Docker images for Roon

(Patrick Lang) #2

Thanks for posting these! I actually found your image + Dockerfile through Docker Hub and got it working right away. I wrote up my AirSonos + RoonServer setup on my GitHub page

Once I move it into Docker-Compose to handle the build+upgrades, I’ll be sure to send you a PR.

(Mike Dickey) #3

Glad to hear it! I’m actually quite thrilled by how well Roon seems to run inside a container. Look forward to your PRs.


For those who try this, please state the size of the library and make any comments on how responsive the system is.

(Jon Boy) #5

With FreeNAS 10.0 moving to the Docker system, it’s nice to see someone has even already created a RoonServer (and RoonBridge) Docker! (Im)Patiently waiting an actual release of FreeNAS 10 (scheduled for February 20, 2017) so I no longer have to use an ancient laptop to host the server software. Thank you, @mikedickey in advance. I too stumbled across your build on the Docker Hub and then came here to see if I could find more info.

Once installed, it will be a library of roughly 650GB (almost exclusively AIFF files with a smattering of DSF) on a FreeNAS machine of ~16TB, 64GB RAM, E3 1220. Cannot yet comment on responsiveness for obvious reasons.

(Patrick Lang) #6

I’m giving 2 cores of an Athlon x3 440 to my VM hosting the container. All files are on a file server using HDDs. My Roon database is on SSD storage and response is pretty much instant. Streaming to multiple devices including DSD & resampling is no problem.

We’re working out problems with Roon 1.3 in containers though, so watch this space for an update

(Patrick Lang) #7

I’m back up and running on 194, and it’s pulling in my collection that I bind mounted into the container now.

I didn’t change the Dockerfile for 194, I just rebuilt with no cache to pull in the Ubuntu updates & latest Roon version all at once:

docker build --no-cache -t roonserver:1.3-194 .
docker tag roonserver:1.3-194 roonserver:latest
docker run --name RoonServer --net=host -d -v roondata:/var/roon -v /mnt/musicarchive:/music roonserver

Here’s the thread where we were discussing issues with libraries in local Linux paths. I think it’s all resolved now.

(Mike Dickey) #8

I just pushed new images/tags for 1.3 to Docker Hub.

(Patrick Lang) #9

Does anyone from Roon want to make this official? I’d be glad to help develop & test, hopefully @mikedickey would be too.

Docker Hub has an autobuild feature that can trigger off a source repo change, as well as dependent images This would help automatically pick up updated Linux images as well as new version of Roon. I know your code isn’t open source, but you could have the Dockerfile and install script on GitHub with a version-specific URL in the script. Update the script when you release a new version and Docker Hub does the rest for you.

Another approach would be to just build these images as part of your normal build & test workflow and publish the ones that pass :slight_smile: It would be a great way for experienced users to try early builds because we can roll back to an older version in a few seconds if needed.

FreeBSD Core Server
(Mike Dickey) #10

Docker Hub’s build machines set some very low (u)limit’s which cause the Roon installer’s pre-flight checks to fail. Hence, I’ve been building and pushing manually for every release. Not sure if those limit checks are necessary or maybe they could be bypassed with a command-line flag? In any case it would be trivial to automate this process, and I’d be happy to help. I’ve been running RoonServer in a docker container for several months now and it works great.

(Patrick Lang) #11

Hmm, I guess I didn’t notice those preflight checks. Since I’ve been building rather than pulling, they’re run on the same machine that I ultimately run Roon on. I’m wondering if that could lead to suboptimal settings. For example, I have both an AMD and an Intel server running which support different levels of SSE, AVX, and so on.

(Mike Dickey) #12

The ulimits will be set by your host machine where you run the container, not by the image. So it shouldn’t impact anything other than Docker Hub being unable to build the image on its own.

(JonC) #14

Mike Have you run onto issues updating the image to 234? I tried recreating an updated image, but my container now just restarts repeatedly. I’ll analyze the log tomorrow and hopefully locate the issue.



(Mike Dickey) #15

I just rebuilt and pushed 1.3-234. Seems to be working ok for me so far.

(JonC) #16

Oh okay, well thanks for the sanity check. At least I know it should work correctly and it’s not the update that caused an issue.
I’m not sure what I did differently, but it was entirely too late at night to be messing with so I probably goofed. I’ll figure it out when I get some
free time.



(JonC) #17

Hey Mike, I accidentally updated roonserver and now I can’t connect. Could you update the image? I’ve been unable to play music and haven’t had the time to figure out why my image stopped working.

(Mike Dickey) #18

1.3-242 is up on ducker hub. I rebuilt and pushed it a few days ago.

(JonC) #19

Oh, thanks for that. I only issued a docker restart command. I forgot I needed to stop and rm ROON container and use the docker run command to recreate it. Thanks for jogging my memory. I appreciate the reply.


(JonC) #20

I so hate bothering you, Mike, can you update docker to 1.3 version 247? I lost Tidal service. My roommates are looking at me funny and they want me to play stuff! Thanks In Advance! :slight_smile:

(Danny Dulai) #21

@mikedickey the way you’ve done your Dockerfile is very standard and reasonable.

I’m wondering if a better way for Roon would be to have the installer download and run at first run of the container, then you’re never have to “update” it on the hub.

(Mike Dickey) #22

@Wh01sjongalt updated to 247.

@danny That would work, but I think it would be better if Roon just took this over and bumped it as part of your existing release process :slight_smile:

Wondering if we could set this up so that you just have to send a REST trigger to DockerHub and it would do all the work for you… I can look into it.