Hi, my admin panel was badgering me about upgrading to 29.0.7. I did. It went well. Now my Docker PHP container won’t run because latest images are only at 29.0.6.
This seems like a silly and absurd problem. Surely I’m doing something wrong? And can anyone tell me if there is a release schedule for the official Docker images?
This is what my container, stuck in a restart loop, tells me:
Can't start Nextcloud because the version of the data (29.0.7.1) is higher than the docker image version (29.0.6.1) and downgrading is not supported. Are you sure you have pulled the newest image version?
And all I can do is put the poor beast out of its misery…
sorry there is no release schedule for Docker community image. often it takes 3-4-5 days after official release. it comes when it comes. IMHO it is best to track the Docker hub Nextcloud tags
it seems you somehow performed an update of your data? please always follow the Docker upgrade procedure
It sounds like it. In the micro-services image (GitHub - nextcloud/docker: ⛴ Docker image of Nextcloud) the Updater isn’t even included in the image because it’s not an appropriate way to update the image (and the web Updater mode is disabled as long as your configs are up-to-date, which you can confirm by checking for warnings in your container start-up logs).
What image are you using?
How did you update, precisely?
And can anyone tell me if there is a release schedule for the official Docker images?
Thanks for the quick follow-up! You both gave me parts of the explanation. I was indeed being a dumbass.
I’ve been following the advice of a sys admin who said to “only ever use the cli updater”. I’m guessing he’s not using Docker.
My current install is a rescue from a hosting service that was less prepared than they said to host nextcloud instances. It took me 2 days of tweaking to rescue the data and get it through 4 major versions on a VPS.
So when I saw I had no updater, I just assumed I had rm’d it by accident, downloaded the zip and rsync’d the folder right into my install… Facepalming hard right now.
Not fully related but would be nice to know: is there any way to either disable the irrelevant update warnings? My memory is mostly swiss cheese, wouldn’t want to force an impossible update again.
Yeah the appropriate workflow seems to be: if your target env is in a container, don’t update until you’ve moved your data and the container will take care of it.
It’s a shame, there are a lot of docs and tutorials out there but so many that to find info like this you kinda need a map. I’ll know now. I wish the web updates notifications had this use case in mind. Docker user updating too early cause they’ve been told to by the app doesn’t sound so far-fetched.
