When updating from 2.4.0 to 2.5.0, it constantly creates backups and the log says that I am already on version 2.4 although the image is on 2.5.0.
I also did a fresh 2.4.0 install and restored my old 2.4.0 instance via the backup tool. The problem persists.
Welcome to the community!
Take a look at this topic and see if it helps.
That one will not help. I hope it’s still pleasant to read tho
But there is a similar topic to yours.
this night watchtower updates my openhab docker container to 2.5 but this ends in a Reboot loop.
message before container crashes
openhab_1 | ++ cmp /openhab/userdata/etc/version.properties /openhab/dist/userdata/etc/version.properties
openhab_1 | + '[' '!' -z '/openhab/userdata/etc/version.properties /openhab/dist/userdata/etc/version.properties differ: byte 141, line 4' ']'
openhab_1 | + echo 'Image and userdata versions differ! Starting an upgrade.'
openhab_1 | + tee /op…
He deleted his openhab userdata folder.
BUT MAKE A BACKUP FIRST.
Thanks for your responses and hello to the community:) I did a fresh install of 2.4, then used to the backup tool restore the backup of the “corrupted” instance and tried an upgrade to 2.5. Same problem.
So without restoring the backup, I can try again from the start. But to keep things and everything, which files are essential? I am using z-wave and zigbee and some add-ons.
Hey, i have the same problem. I use the tag 2.5.0-armhf-debian from DockerHub.
Even on a fresh install without restoring anything, I still get “You are already on Openhab 2.4.0.”
How does the script find out? I really would like to solve it. Openhab Updating via Docker is unusable at the moment