[image] But clicking on upgrade produces: [image] Now, obviously, I could just follow the instructions and do the git pull and rebuild, but where has this come from? I just upgraded to 1.8 from 1.7.x without any problems a week ago, so how is it suddenly “running an old version of the Discours…

[image] peternlewis: so how is it suddenly “running an old version of the Discourse image”? Must be a timing thing around when we released an update to docker manager. Bottom line is you are running an old version of Ruby in your image and we need that updated.

OK, weird. Anyway, I did as specified (git pull/launcher rebuild) and all went well. Now it says “v1.8.1 + 13”. What does the “+ 13” mean?

That there’s been 13 commits between the v1.8.1 tag and the code you’re currently running.

OK, but as far as I am aware, I’m only meant to be running the current release version, that’s how it’s configured. I take it “git pull” method doesn’t honour this? Though this also happened when I upgraded to 1.8.0, so I’m not sure what happened with that…?

What does your app.yml look like, specifically the params section?

params: ## Which Git revision should this container use? version: stable The entire thing, with some comments and the “env” section omitted is. ## this is the all-in-one, standalone Discourse Docker container template templates: - "templates/cron.template.yml" - "templates/postgres.templat…

That’s because we backported some bug fixes.

Everything looks fine to me and it’s working as intended. The version parameter is actually the name of a git branch to get the code from, and what’s happened is that we’ve put some bugfixes into that branch (as @zogstrip described) but haven’t yet tagged the release (because there’s probably more …

OK, all good, I am back up to date (well ahead of date actually :wink: and have a better understanding of what’s going on. Thanks.

[image] zogstrip: That’s because we backported some bug fixes. I noticed something really odd yesterday on my sandbox. I had just done a GUI update, all went well. When it was done it showed the blue “Upgrade to the latest version” button to the right, but when I clicked the git compare butt…

And the same issue again from 1.8.4 to 1.8.6. You are running an old version of the Discourse image. Upgrades via the web UI are disabled until you run the latest image. To do so log in to your server using SSH and run: cd /var/discourse git pull ./launcher rebuild app More info on our support s…

Discourse ne peut pas passer de la version 1.8 à 1.8.1 ?

Soutien

peternlewis (Peter N Lewis) Septembre 2, 2017, 11:39 15

Second try is the charm.

3 « J'aime »

Sujet		Réponses	Vues
Upgrades via the web UI are disabled until you run the latest image Support	6	1802	Octobre 31, 2017
Cannot upgrade due to old version of docker Self-hosting	5	1574	Juillet 6, 2018
Upgrade link no longer works Self-hosting	7	906	Novembre 22, 2021
Failed upgrade from 2.9.0.beta14 to 3.1.0.beta Self-hosting	11	1150	Février 24, 2023
Trouble upgrading from 3.3.0.beta1 to 3.3.0.beta6 Self-hosting	22	295	Août 8, 2024

Discourse ne peut pas passer de la version 1.8 à 1.8.1 ?

Sujets connexes

Discourse ne peut pas passer de la version 1.8 à 1.8.1 ?