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.

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 …

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

[imagen] 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 …

¿Discourse_docker no fuerza la actualización de la línea de comandos?

Soporte Instalación

Falco (Falco) 15 Abril, 2022 15:09 2

Tienes que actualizar docker_manager primero para poder verlo. Después de actualizar docker_manager, la próxima solicitud a /admin/upgrade mostrará el mensaje.

Tema		Respuestas	Vistas
Upgrade page claims nothing to be done Self-hosting	2	469	3 Septiembre 2021
After updating Docker with one-click update, no Versions are showing Support	8	1029	7 Diciembre 2019
Unable to upgrade docker_manager Self-hosting docker-manager	4	1100	16 Noviembre 2022
Upgrade link no longer works Self-hosting	7	1076	22 Noviembre 2021
Upgrade of docker manager beta7 >> beta9 fails Self-hosting	7	1255	8 Enero 2020

¿Discourse_docker no fuerza la actualización de la línea de comandos?

Temas relacionados