I first click via the admin UI to upgrade docker_manager, and it runs for a while before I see this: Done compressing docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js : 0.17 secs Skipping: plugins/docker_manager-25504a87a4e36bcc8a621591ad8ca39652edee1eb2672…

Can you try a rebuild from the console cd /var/discourse ./launcher rebuild app

[imagen] sam: ./launcher rebuild app Thanks. Not sure why I didn’t think of that. The first time it ended by saying I needed to run it again to finish the update. After running it the second time, the site is all up to date.

No se puede actualizar de 2.5.0beta2 a 2.6.0beta1

Soporte

sam (Sam Saffron) 2 Julio, 2020 23:54 2

¿Puedes intentar una reconstrucción desde la consola

cd /var/discourse
./launcher rebuild app

Tema		Respuestas	Vistas
Upgrade Error from 2.4.0.beta8 to 2.4.0.beta9 Support	1	483	15 Enero 2020
2.6.0 beta 3 update failed on disk and/or memory space Self-hosting server-resources	28	2966	26 Septiembre 2020
Docker Manager: FAILED TO UPGRADE Self-hosting docker-manager , server-resources	6	1419	4 Noviembre 2020
Upgrade of docker manager beta7 >> beta9 fails Self-hosting	7	1255	8 Enero 2020
Blank upgrade page after updating docker manager to 2.0.0.beta10 Bug	15	1195	17 Mayo 2018

No se puede actualizar de 2.5.0beta2 a 2.6.0beta1

Temas relacionados