It seems that this is a security issue that requires a command-line upgrade, but I’m seeing a forced rebuild on only a couple of the sites that I’ve checked, and those seem really old. Continuing the discussion from 2.9.0.beta4: Security Fixes, Sitemaps, Discourse Connect Provider 2FA, and more : …

You have to update docker_manager first in order to see it. After you update the docker_manager, the next request to /admin/upgrade will show the message.

Darn. Ok. I guess the old one can’t know that until the upgrade.

[image] Falco: You have to update docker_manager first in order to see it. After you update the docker_manager, the next request to /admin/upgrade will show the message. This might explain something I saw: I did the docker update, navigated successfully back to the versions tab and then did t…

Discourse_docker not forcing command line upgrade?

Support Self-hosting

geoff777 April 15, 2022, 3:12pm 3

I updated an instance today from the console.
I expected to see a message but didn’t get one.
I did a ./launcher rebuild app just to be safe …

Topic		Replies	Views
Upgrade page claims nothing to be done Self-hosting	2	469	September 3, 2021
After updating Docker with one-click update, no Versions are showing Support	8	1030	December 7, 2019
Unable to upgrade docker_manager Self-hosting docker-manager	4	1100	November 16, 2022
Upgrade link no longer works Self-hosting	7	1076	November 22, 2021
Upgrade of docker manager beta7 >> beta9 fails Self-hosting	7	1255	January 8, 2020

Discourse_docker not forcing command line upgrade?

Related topics