mackid1993

I'm not really supporting this anymore. I don't even use Roon anymore. It's kind of gotten to become garbage. Regardless, I just kind of have it on maintenance mode. They're making their own container, so this is going to be pointless soon. It would be illegal for me to redistribute their binaries. So like with any container for Roon, you update Roon from inside Roon. The only updates that this container pushes are for the base image and any dependencies. And for the other guy, you add SMB shares from inside Roon like you do with Roon.

It's not going to work in bridge mode and you can't use Tailscale inside docker in host mode. For ARC what you'll want to do is install Tailscale on Unraid and use that IP address. Set up subnet routing. You should be good to go with subnet routing.

I have no idea why BackBlaze doesn't see Virtiofs mounts. Maybe they cracked down since they aren't NTFS formatted. I don't even use VirtioFS anymore since the drivers suck. It would sure be nice if random people would STOP DMing me every day asking why! I'm just another Unraid user.

I mean a reverse proxy isn't going to really work with Roon (at all). This again has nothing to do with the container is should be addressed on the Roon forums. Most issues are not related to the container and are Roon issues. Keep in mind that this Docker does not contain Roon at all. That will be against Roon's licensing. The container contains the base OS and dependencies needed for Roon. Roon is downloaded on first start and stored outside of the image. There is very little that could possibly go wrong with the container. It's really very simple. The only Issues that could possibly occur as a Photon OS update or a dependency update, but those are generally unlikely.

You can test. I've only used host.

Sorry, I just saw Roon just released a new early access version that addresses a memory leak with Chromecast devices. I'm not sure if that's applicable to you. https://community.roonlabs.com/t/earlyaccess-roonserver-2-53-build-1541-and-arc-1-68-build-361-is-live/302420

That's not the container. It's Roon that does that.

Just an FYI, sorry for pushing several updates over the last day. I realized the original FFmpeg distribution that this container was using hasn't been updated since 2024. I switched to an actively maintained one, and that just required a little bit of testing, so I ended up pushing a few more tags than the one a month I normally would have. Everything should work fine now, but if anyone notices anything weird, please post here. To switch, I had to make a lot of changes to the Dockerfile. I also threw in a check to make sure FFmpeg actually works. If it doesn't work, the build will fail, which is good because I don't want to push a build where FFmpeg isn't working.

If you look at the original post, I updated it to list out more clearly what the differences are. This was a good question, so I felt like it should be addressed properly.

The only concern I have is if the website that it pulls FFmpeg from goes down for some reason and the container builds without FFmpeg. However, Photon doesn't have a native FFmpeg binary in its package manager. So this is really the only way to do it. Fortunately, it seems like this guy's website is like the default place to get FFmpeg from pre-built, so I doubt that it'll be an issue. However, that's the risk with automation. What you would do is just go over to Docker Hub and append one of the older tags to the template in Unraid's Docker manager, and it would just pull the older version of the Docker container, for example, the one from the previous month. If that were to happen, it would be pretty obvious, and I would look for a way to fix it, obviously. I did some research, and there are other people that provide FFmpeg static builds, so we would have a solution pretty quickly. The only other issue I see potentially is Photon OS is made by VMware which is owned by Broadcom. So if Broadcom were to cause some sort of issue, then obviously we'd have to probably switch to Debian Slim like the other container. Although I'd look into Alpine as I believe that is very lightweight as well. If that were ever to happen, I would probably disable the auto updates until I could figure out what to do.

If anyone is interested my container is now published on CA. Support thread is here: https://forums.unraid.net/topic/190570-support-roonserver-photon-os/

Yes, Roon is paid software. This thread is for issues with the container specifically. For questions about Roon it's best to visit the Roon community.

I sent a DM to @Squid about ten days ago to try to get my Docker container for Roon published to community applications because the one that's currently up there hasn't seen any updates in about two years. The maintainer of that template actually hasn't responded to any requests on the support thread or over direct message to try to swap out that Docker container with something more actively maintained. I put together a container based on another one that was recommended on the Roon Labs Community Forums. It's based on Photon OS, and I have used GitHub Actions to automatically push a new image of it on the first of each month to Docker Hub, so all the dependencies, OS, etc are always patched. This is my first time doing this, but I'm almost certain my XML is correct, and I've sent everything over to Squid. The XML is published to GitHub in its own repository and I've also created a support thread which needs to be moved. It's located here currently: https://forums.unraid.net/topic/190570-support-roonserver-photon-os/ I'm just trying to get this out there so other people can benefit from it. My main reason for doing this was I was actually running into some compatibility issues with the current container on CA likely because it just hasn't been updated in so long, I believe some of the dependencies are no longer compatible with Roon. Additionally, the maintainer of the template for Unraid isn't the maintainer of the docker container itself. It seems like the maintainer of the docker container itself may no longer be interested in updating the container based on what we're seeing In the broader Roon community. I'm hoping Squid can help me get this published just to benefit others in the community that may be interested in a more up-to-date and secure container. Thank you.

RESERVED

RESERVED

RESERVED

Edit: I am no longer maintaining this container. Please see: https://help.roonlabs.com/portal/en/kb/articles/installing-the-roon-server-via-docker for using the Official Roon Docker. It's come to my attention that Roon is developing their own container, so there's really no point in me supporting this anymore. I also don't regularly use Roon anymore, but the container will continue to update because it's automated through GitHub. Anyone is free to use this while it continues to work. And then when Roon releases their container, I would strongly recommend moving over to that. I may consider using Roon again when they actually invest in their platform. Hopefully they do. It seems like they may be starting to again. Also, the container updating does not update Roon, it just updates the base image and dependencies. Roon always updates from inside Roon. Roon is a premium music management and streaming platform designed for audiophiles and serious music lovers. It provides a rich, visually engaging interface that transforms digital music collections into a highly interactive experience, combining local files, streaming services like TIDAL and Qobuz, and extensive metadata to create a centralized, deeply informative library. This is a support thread for my RoonServer docker built on PhotonOS. Github Repo: https://github.com/mackid1993/docker-roonserver For detailed info about the container, please read the ReadMe on Github. Docker Hub Repo: https://hub.docker.com/r/mackid1993/docker-roonserver/ For support and troubleshooting related to Roon or RoonServer itself please visit: https://community.roonlabs.com Please be aware that Roon Labs does not provide official support for Roon running under Docker and any official support requests made to them may require you to reproduce your issue on a supported platform. This thread is intended for support related to the container itself as it relates to Unraid, not Roon specifically. Please do not ask general questions about Roon here. Differences Between steefdebruijn/docker-roonserverThis container uses Photon OS instead of Debian Slim (https://vmware.github.io/photon/). Photon OS is extremely lightweight and many in the Roon community have found that resource usage (particularly memory) is much lower with Photon OS than with Debian Slim. A new image will be pushed on the first of every month using GitHub Actions, this happens roughly at 12 a.m. EST or 1 a.m. EDT. However, this means that this container may also potentially break things as it is being updated more frequently. It's a trade-off between greater security and potentially causing compatibility issues if one of the dependencies causes an issue with Roon. If you are using Roon ARC, and have a port open on your router, it is a good idea to have the container up to date with the latest security fixes. This container also uses the latest FFmpeg version available from the master branch at the time it was pushed. This ideally allows for the latest bug fixes and features in FFmpeg to be made available. However, given that it's the latest version, there is a possibility that there could be a bug introduced by the FFmpeg developers. Both philosophies obviously have trade-offs, and I want to make that clear here before anyone chooses to use this container. It's a choice between frequent patching and more time between updates but potentially greater stability. In the case of Unraid, I am maintaining the template as well as the Docker container. In the case of the other container, the maintainer of the template is different than the maintainer of the Docker container. They have no control over when the Docker gets updated. The last three tags will be always kept, so if an update breaks something you may revert manually to the last working tag until a solution is published. I am a Roon Lifetime license holder and use it everyday so if something breaks, believe me I'll know and I'll be doing my best to fix it as soon as I can, since I want Roon to work as much as everyone else does. This is a drop-in replacement for the existing RoonServer docker, so if you have that running you may simply change the template to point to: mackid1993/docker-roonserver if you would like to switch. This container is ultimately derived from steefdebruijn/docker-roonserver so all paths are the same. You can remove the old container and add this container and just set /backup and /music if you want it as well. This container would not be possible without the work of Steef de Bruijn and David Ferreira on their RoonServer containers. It is ultimately derived from those containers, now with some modifications. I really appreciate all of the work both of those individuals have done for the Roon/Home Lab community. RoonServer on Photon OS would not have been possible without https://hub.docker.com/r/davindisko/roon-photon.

I tried reaching out to the developer of the RoonServer template: https://forums.unraid.net/topic/129853-support-xthursdayx-roonserver/ It is based off of this container: https://github.com/steefdebruijn/docker-roonserver that is as far as anyone can tell is abandoned and hasn't seen a fresh build in 2 years making it vulnerable and also in my experience the cause for compatibility issues with Roon possibly due to outdated ffmpeg. Another Roon user made this drop-in fork: https://github.com/davindisko/docker-roonserver based off of Photon OS that works extremely well. It was discussed in the Roon community here: https://community.roonlabs.com/t/docker-image-for-roon-server/176876/11?u=mackid1993 and found to be much more efficient in terms of resource usage over the older Debian container. I decided to take this container and implement Github actions to rebuild it each month automatically and push to Dockerhub so it would always be up to date. RoonServer updates independently of the container but the various dependencies as well OS obviously don't. My repo is here: https://github.com/mackid1993/docker-roonserver I'm inexperienced with Docker but did reach out to the CA maintainer several weeks ago to try to get this template updated with something maintained and haven't heard back. I'm wondering if someone in the Unraid community with the ability to help and Docker experience can assist with getting this template updated. The container I forked is a drop in replacement for the existing one. Just simply pointing to my Dockerhub repo and updating does nothing to break Roon but will replace the existing container with a patched one. Hopefully someone will see this and be able to help! Thanks!!

My container https://github.com/mackid1993/docker-roonserver (found on Dockerhub mackid1993/docker-roonserver:latest) automatically rebuilt like it was supposed to on May 1st along with new dependencies and the latest Photon OS build. Running this since mid April I've seen zero issues and the issues I was running into with the original container that is unmaintained haven't come back.

That's only when using Tailscale in the container. You can still use Tailscale on the whole server just fine.

https://community.roonlabs.com/t/ticket-in-b1526-adding-an-artist-to-a-playlist-causes-an-immediate-crash-windows/297851 They put a ticket in for my report.

@KingHawk I can reproduce that crash. It looks like a Roon bug. I don't really use playlists but perhaps try setting up a temporary server on a PC or Mac and see if you can reproduce the issue. If you can then let Roon know.

I have no idea. That sounds like a Roon issue. Roon doesn't support docker so they may or may not choose to help you.

This guy made the container I'm using: https://github.com/davindisko/docker-roonserver I just made a new repo and added the github actions to force a rebuild so it doesn't go out of date. His container is based off of Steef's so it's a drop-in replacement on Unraid. His Dockerfile is also very easy to understand so any issues that arise should be very easy to fix. It should be very set and forget.