Yeh, sorry about that. I think it's due to the fact that the image is not hosted on docker hub. When the check for update script runs, I would image it only compares the current image to whatever is on docker hub. As those don't match it says that an update exists even though it doesn't. As I don't maintain the image, there is nothing I can do about this. All I can suggest is turning it off automatic updates, so it doesn't attempt an update all the time. And just updating it manually periodicall