Hi @PaulK,
I actually just tested installing this Rockon and was about to get back to you when I saw your update. There seem to be two different things happening here (1) discrepancy between what Rockstor has in its database and what is actually installed (likely due to the first failed install), and (2) the initial problem you had with the install (your first post).
The first step would be to clear problem #1 by removing all traces of the Rock-On on your system so that we can start fresh. Before doing so, however, could you please provide some more details on the following?
I suppose you meant clicking the “Update” button on the top right of the Rock-ons webUI, is that correct?
Do you mean uninstalling the docker container manually with docker rm linuxserver-mariadb
?
Regardless of the above, there is a handy but powerful little script to wipe any trace of the container in both your system and Rockstor database, as described by @phillxnet
/opt/rockstor/bin/delete-rockon
Delete metadata, containers and images of a Rock-on
Usage: /opt/rockstor/bin/delete-rockon <rockon name>
In you case, I believe the rockon name
should be linuxserver-mariadb
resulting in the following command:
/opt/rockstor/bin/delete-rockon linuxserver-mariadb
Regarding problem #2–your initial install of the RockOn–we would need to know a little more about what you used to know what went wrong.
The container’s logs could be helpful (docker logs linuxserver-mariadb
) but you would need to look at them before running the delete-rockon
script above.
As I mentioned above, I just tried to install it on my test VM and it worked without a problem. I used the following settings:
- created a new share on my main pool (different from the rockstor_rockstor pool)
- set UID and GID to 1000 (corresponding to my main user)
Let us know how the first cleanup step goes and we’ll try to go further from there.