Unfortunately, there isn’t really a one-size-fits-all type of answer on how to update a project running in a docker container (and thus rock-on, indirectly): I now know the best practice for updating so hopefully will keep things cleaner in future. This probably stemmed from my initial use of Emby and trying to get it updated properly (improperly in my case). Sorry if I got a little confusing in my notes above, but I hope this helps, what is the output of the following command?.what is the name of the Emby rock-on displayed in Rockstor’s webUI? Exact letter casing would be needed.If you’re interested, you can verify a few things: 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. 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?). ![]() It seems you encountered some sort of conflict (at some point) resulting in conflicting information in the database. A clue to explain that may reside in your following quote, however:Īltogether, it suggests that you still have the old version listed in your database, and this is why you are seeing this error message. In your case, I would have believed it should have done so. ![]() 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. pulling a new image only if a newer version exists. We do trigger a docker pull command at install, however, so that we can take advantage of docker’s default behavior, i.e. 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. Mmmm, something seems odd, indeed, as you said. ![]() Something must have been stale, meaning I wasn’t getting the properly updated docker image/instructions. Anyhow, it doesn’t seem to be causing issues so I will leave that one for now.Īlthough 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”. Which is puzzling given I purged the embyserver container from the DB. It belongs to another Rock-on (EmbyServer). Now the UID and GID match what I choose, and I get the option for additional GIDs that was never showing up before.ĮRROR Exception: Duplicate container (embyserver) definition detected. opt/rockstor/bin/delete-rockon embyserverĪlthough 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”. The solution was not just removing the rock-on via the GUI, but utilising I finally fixed it yesterday, though there’s still a puzzling error in the logs. Searching the emby forum didn’t turn up any similar issues. I did appreciate the information you provided. ![]() So I took way too long to investigate this more, sorry I took so long to reply.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |