@D_Jones Hello again.
I have finally created an issue set for this usability shortfall, I was fairly sure we already had one in rockstor-core but apparently not, so here it is:
and it’s partner in the rockstor-doc repo:
Would you mind changing the title of this thread to reflect only the snapshot removal (ie “remove update or”) as this is enough to explain your reported issue here. Also we have had a long standing problem with needing to reboot after each update which affected docker functionality but usually simply switching it on again sorted this but not always.
As for getting things back in order I would suggest making a new rock-ons-root share and re-establishing your rock-ons using their existing config and data shares. Attempting to uninstall what ones you can would be good first of course. That way the root or ‘system part’ of all the rockons / dockers should be re-established on the new differently named share.
Hope that helps and we definitely have a way to go on the robustness / available clean up tools front for the Rock-ons / docker subsystem but hopefully bit by bit we can get this into proper shape.
Thanks for reporting your issues.