I’ve been running your extension on my Synology NAS for 3 years with no issues. I was not running the latest build therefore went ahead and updated manually the package. The Extension Manager starts and runs fine, however I’m facing an error when starting extensions. The installation of the extensions goes fine but at start up I’m getting the following error message:
Bind mount failed: '/home/node/.rem/binds/roon-extension-alarm-clock/usr/src/app/config.json
Manual installation of the Extension manager was done in the same manner as the previous version:
Everything seemed to install fine. I checked all the upgrades/updates and rebooted several times, but never see extension manager in Roon. I have a sense that it might be an issue with my Docker container, but am not really sure.
So I’m looking for guidance on a few things:
How do I know if Roon Extension Manager and other required systems are installed properly?
If something needs to be launched or run (like a Docker container), is that handled by REM or is that a separate step?
I’ve read just about everything I can find, but am still struggling, so thanks in advance for any guidance!
Hello everyone,
Is it possible to know the list of extensions installed by the manager ? Including their category.
Let me explain :
a few days (weeks ?) ago I installed several extensions to play with.
A few days later I stopped them, which means that they are no longer visible in Roon.
Now I would like to uninstall them but I do not remember their name or their category.
Is it possible to have this list ?
For information I use DietPi v9.3.0 on RPi 3 Model B.
Thank you in advance for your help. dp
This cannot be done in the Extension Manager. Easiest I can think of is list all Docker containers that are created and use that as a hint for cleanup. The command to use is: docker ps -a
You can also use the name from the NAMES column to remove manually, like this: docker rm <name>
After manual removal you have to restart the Extension Manager to let it pickup the changes.
Hi all
As a not very experienced user, I tried to install the extension-manager on Ubuntu using docker.desktop and I failed …
Maybe somebody has a hint where to look. Here the message:
When installing the Extension Manager you have to use the v1.x-standalone tag, the full name then becomes theappgineer/roon-extension-manager:v1.x-standalone.
I removed the latest tag to prevent that outdated software is installed by default.
Thank you very much for the fast response. I will try your advice.
In the meantime I installed the extension manager using the command line, following your guidelines. The installation was successful and it was easier as anticipated. Obviously the easy way using a GUI is not always simpler. I guess I got spoiled over the past years.
Again THANKS.
If you got it working using a command line install I would stick with that. There are some specific options required that are not always provided in GUI installs.
I’m having a problem with REM. I’m getting the “Extension Manager requires Docker!” error. I specify GROUP_GID=0 as an environment variable when I install it. It had previously been working and I tried reinstalling when I noticed the error. I didn’t need to specify group_id when I initially installed it a year or so ago. I’m not sure when this started as the Deep Harmony extension I use has continued to work. I’m using the v1.x image in Container Station 3 on an Intel x64 QNAP (TS-664). I’ve also tried the v1.x-amd64 image with the same result. Same goes for the standalone version.
It seems this was a problem with the Container Station 3 GUI. Once I ssh’ed into my qnap and:
removed the old Container
pulled the new image, then
ran the docker command “–network host --restart unless-stopped --name roon-extension-manager --group-add 0 -v rem_data:/home/node/.rem/ -v /var/run/docker.sock:/var/run/docker.sock -e “TZ=Canada/Pacific” theappgineer/roon-extension-manager:v1.x-standalone”
Everything seemed to work. I needed to remove the "–log-driver journald " option as journald wasn’t installed.
In any case I seem to be up and running again - now onto getting Deep Harmony working properly again as it also had stopped working - but now I have REM running properly, I don’t think that will present any major problems.
Hi @Bob_Hornibrook
Good to hear you got it working again. The critical part is the mount of the docker socket, if that is missing the Docker installation cannot be found.
Thanks for taking the time to respond. You are correct, I had missed that when using the GUI. Funny, I don’t think I used it when I first set up the container last year. Live & learn. Until now, I had always used the GUI for containers, the using the command line wasn’t anything I had considered. Always good to learn something new though.
If I was to add it with the GUI, I assume it would be as a volume that mounts a host path, would this example below be correct?
Nothing important to contribute here, just saying thank you. Got this working on a Synology NAS super easily and really impressed how it spins up the extentions from the Roon extentions interface. Mainly installed to get a web player on my local network but sat around and messed with some extra extentions. If anyone has trouble with the manager on Synology, it’s way easier to install via SSH as shown in the wiki, but I’d bet if you were careful with permissions (Docker user 0) and add the TZ as a environmental variable. I also tried to use the :latest image but the 1.x-standalone as the wiki said seemed to be the one that worked.
Anyone else noticing that suddenly today the Roon Extension Manager is crashing a lot? I used to see the occasional crash (no big deal), but it’s crashed probably 10 times today. Most recently at 8:51pm. Here is a screen cap of the logs from the docker container showing the crash & restart:
