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