Emby rock-on UID and GID

[Flox]

Hi @mattyvau,

I’m glad you could get this fixed!

Thanks a lot for the follow-up and all the details… they actually give me a few ideas as to what could have happened so I’ll try to provide some information below.

@mattyvau

Although emby was updating to new versions if I removed and re-installed the rock-on, it wasn’t until I cleared it more thoroughly with delete-rockon that re-installing actually pulled in the changes to add rock-on “wizard”. Something must have been stale, meaning I wasn’t getting the properly updated docker image/instructions.

Mmmm, something seems odd, indeed, as you said. Currently, Rockstor does not delete a docker image upon a rock-on uninstall in order to make a subsequent re-installation faster and avoid unnecessarily re-downloading the same image. We do trigger a docker pull command at install, however, so that we can take advantage of docker’s default behavior, i.e. pulling a new image only if a newer version exists. If you’re interested, you can get more detailed on the underlying code in the related wiki post, under the Building the docker command section. In your case, I would have believed it should have done so. A clue to explain that may reside in your following quote, however:

@mattyvau

Now the UID and GID match what I choose, and I get the option for additional GIDs that was never showing up before.

Indeed, the option to add a list of GIDs was added a little while ago now after a refresh of the related rock-on definition file (see below).

Update to EmbyDotNET version

The fact that you did not see this new option means your system didn’t refresh its rock-ons definitions. This process is completed every time one clicks on the Update button in the top right corner of the Rock-ons webUI page (more details on this process in the wiki post as well, section “Rock-on definition fetching”). Would you remember whether or not you clicked this button after uninstalling the Emby rock-on?

Another clue to explain everything, however, hides between two more pieces of information you gave (thanks again!):

@mattyvau

The error I am seeing still is:

ERROR [storageadmin.util:44] Exception: Duplicate container (embyserver) definition detected. It belongs to another Rock-on (EmbyServer). Uninstall one of them and try again.

Which is puzzling given I purged the embyserver container from the DB.

and

@mattyvau

The solution was not just removing the rock-on via the GUI, but utilising

/opt/rockstor/bin/delete-rockon embyserver

Everything starts to make sense after noting the letter case used. Indeed, it is important to note that the delete-rockon script is case-sensitive, meaning that using that command should have removed the rock-on named embyserver. Did this script return an error or a confirmation that Rock-On(embyserver) metadata in the db is deleted'? While embyserver is the name used by the underlying container, I do not recall the rock-on being named this way. It actually used to be named EmbyServer… curious.

Interestingly, in the same refresh of the Emby rock-on definition linked above (and repasted below), you will see that the rock-on name changed from EmbyServer to Emby server.

Note how the former corresponds to the name listed in your error message?

@mattyvau

ERROR [storageadmin.util:44] Exception: Duplicate container (embyserver) definition detected. It belongs to another Rock-on (EmbyServer). Uninstall one of them and try again.

Altogether, it suggests that you still have the old version listed in your database, and this is why you are seeing this error message. It seems you encountered some sort of conflict (at some point) resulting in conflicting information in the database.

This also means that I am a little puzzled by how this happened and how you have the Emby rock-on installed besides this error message (does it still appear in your logs, or is it from quite some time ago?).

We should be able to clean it up, however, but as I don’t want to create more problems, maybe we should make sure of what the current status is. If you’re interested, you can verify a few things:

• what is the name of the Emby rock-on displayed in Rockstor’s webUI? Exact letter casing would be needed.
• what is the output of the following command?

docker ps -a | grep emby

Sorry if I got a little confusing in my notes above, but I hope this helps,