hey @herbert, I applaud you for trying a few variations and reporting back very useful information.
The fact that you are not seeing the eternal spinning gear is indeed a good sign 
The ācould not find imageā error indicates that something went wrong in the Rock-On root share. May be some snapshots got deleted? Since all the application data of your Rock-Ons is mapped via Shares, there is no harm in just starting over with a new root share. All your app data should still be there(you may want to start fresh with config shares, howeverā¦ this is app specific and not really in our control).
These are the steps Iād follow (also read this doc for general tips about the root share, best practices etcā¦)
- Uninstall all Rock-Ons.
- Turn off the Rock-On service
- Create a new Share to use as Rock-On root share.
- Configure the service to use the new root share
- Delete the old root share(youāll need to delete all the snapshots inside it first)
- Start the service
- Click Update so all app profiles are updated.
- Install your Rock-Ons. Use the same Share mappings to retain app data.
Regarding your last comment, your frustration is understandable. There is volatility with the Rock-Ons framework which we addressed quite a bit in .11 cycle. One of the key changes that I think is directly related to your problem is how we ship docker binary. It is after all third party software and rapidly evolving. Previously we used to deploy/redeploy from the upstream. Now, we are regulating that just like we do the elrepo kernel. Any updates to docker go through the testing channel first. The other thing to note is that each Rock-On is backed by third party docker images. The core team tests as much of these as possible, but it is a lot of work, itās not the core of Rockstor and we shouldnāt be assumed as the maintainers of individual Docker images. Our goal is to provide a robust and generic way to host and manage these apps via the Rock-On framework. Anyway, thanks for your patience and report back how it goes!