I do know that it’s because of Alternative Logos: I, [2021-06-25T11:00:32.360020 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake themes:update assets:precompile' Failed to update Alternative Logos about.json contains invalid values: Maximum discourse version is invalid /…

Ok, so the solution was to set up a fresh discourse installation, restore from backup and then delete component that was causing an issue.

[imagem] pawelorzech: ./launcher cleanup I’m not sure what cleanup does to stopped containers, but you might just ./launcher start app and disable the culprit ( in https://your.domain/admin/customize/themes ) ? [imagem] pawelorzech: disabled all extensions Do you mean the plugins in t…

[imagem] Benjamin_D: Do you mean the plugins in the app.yml ? Yup. I do know that it’s because of Alternative Logos: I, [2021-06-25T11:00:32.360020 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake themes:update assets:precompile' Failed to update Alternative Logos…

So: I can’t rebuild because Alternative Logos has about.json max version that I’m above I can’t delete Alternative Logos component without entering the app I can’t enter the app because I can’t rebuild it Is there any way to do something here? I want to get rid of Alternative Logos component.

Can’t you just start the app, without rebuilding it? [imagem] Launcher cleanup description: images & containers > 1h Bug The launcher help text indicates that cleanup command removes containers that have stopped for > 24 hours: But the issued commands …

./launcher start app Unable to find image 'local_discourse/app:latest' locally docker: Error response from daemon: pull access denied for local_discourse/app, repository does not exist or may require 'docker login': denied: requested access to the resource is denied. See 'docker run --help'. Not r…

Then maybe git pull but perhaps wait for the cavalry :sweat_smile: (I see Jay replying…)

Have you tried ./launcher start app Though if you did a ./launcher cleanup while the old container was down and don’t have a container to start then you are in something of a pickle. Is that what you did? It looks like what you did. I think that it’s a bug that a bad theme component would make …

I guess I’m gonna do a fresh install, restore from backup from (and in this .sql backup file I’m gonna make changes to Alternative Logos. It is a really bad situation though that if a component breaks discourse rebuild you don’t have any other option but reinstall from fresh.

I ran into a similar situation this morning, but I was able to simply restart the app. My site has about 10 themes, all of which have been using the Alternative Logos Component since every theme uses different colored logos to match its color scheme. I see where I can now input the dark theme logos…

Não é possível excluir o componente de tema obsoleto do CLI - falha ao inicializar

Suporte

pawelorzech (Paweł Orzech) Junho 25, 2021, 2:06pm 13

Ok, então a solução foi configurar uma instalação nova do Discourse, restaurar a partir do backup e depois excluir o componente que estava causando o problema.

Tópico		Respostas	Visualizações
Error when "./discourse rebuild app" due to theme error Self-hosting	5	1877	1 de Dezembro de 2021
Path of theme components Support	19	2074	12 de Agosto de 2021
./launcher Rebuild App Failed During `rake themes:update assets:precompile` Self-hosting unsupported-install	10	1583	20 de Dezembro de 2021
After upgrade every component is broken Self-hosting	5	211	13 de Julho de 2026
Blank website after update Support	14	1818	26 de Agosto de 2020

Não é possível excluir o componente de tema obsoleto do CLI - falha ao inicializar

Tópicos relacionados