Yes, linuxserver.io tends to have auto-update on startup only in the instance that the application cannot self-manage updates.
This makes sense, as there’s no need to bother writing the update script for something that already has the capability.
It’s worth noting that the auto-update on startup will also not update the image itself. The auto-updater in the plex docker for example still uses the original container image, but on startup will retrieve the latest package from plex.tv and install it.
Uninstalling and reinstalling will pull the latest dockerfile for that container including it’s install procedure.
Does it? I only run the Emby container for a short while, I found that it was extremely slow to scan for media, and the client application interfaces were enourmously slow on libraries containing >3000 individual items.
This is true, and you’ve outlined the reasoning perfectly. It’s not Rockstor’s responsibility to provide this information. I do however think that each Rockon should have a link to it’s dockerhub page describing the usage a little.