Current rebuild of web-app fails with this error: root@docker2:/var/discourse# ./launcher stop web_only && ./launcher rebuild data && ./launcher rebuild web_only x86_64 arch detected. + /usr/bin/docker stop -t 600 web_only web_only x86_64 arch detected. Ensuring launcher is up to date Launcher is u…

You should be able to get it back up with ./launcher start app That will restart the old container. I don’t know what the actual problem might be, but it could be a regression.

[imagen] Jay Pfaffman: ./launcher start app In this case web_only and data are separated containers and the startup of the web_only container fails with oot@docker2:/var/discourse# ./launcher start web_only x86_64 arch detected. starting up existing container + /usr/bin/docker start web_onl…

[imagen] Thommie Rother: In this case web_only and data are separated containers Sorry. I didn’t know that part (or maybe didn’t read carefully). Then you need to ./launcher destroy web_only;./launcher start web_only Unless you’ve run a cleanup that deleted the container, in which case yo…

[imagen] Jay Pfaffman: /launcher destroy web_only;./launcher start web_only @pfaffman thanks, that fixed it. I forgot that the data container also provides the redis caching functionality - but anyway, now the containers are running again. What can we do with the bootstrap error from launche…

This is not the error, it’s just a warning [imagen] Thommie Rother: /launcher: Zeile 334: Warnung: Kommandoersetzung: NULL-Byte in der Eingabe ignoriert This is the error. [imagen] Thommie Rother: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups/cli.rb:54:in `split': invalid byte…

yep: root@docker2:/var/discourse/containers# yamllint web_only.yml web_only.yml 5:81 error line too long (115 > 80 characters) (line-length) 8:1 warning missing document start "---" (document-start) 14:4 warning missing starting space in comment (comments) 14:3 …

El lanzador falla: línea 334: byte NULL ignorado

Soporte Instalación

pfaffman (Jay Pfaffman) 4 Octubre, 2024 16:15 2

Deberías poder recuperarlo con

./launcher start app

Eso reiniciará el contenedor antiguo.

No sé cuál podría ser el problema real, pero podría ser una regresión.

Tema		Respuestas	Vistas
Docker launcher fails with message «/pups/lib/pups/cli.rb:15:in `split': invalid byte sequence in US-ASCII» then container *.yml file contains non-ASCII symbols Bug docker	3	2358	10 Junio 2015
Launcher upgrade failing Self-hosting two-container	5	220	5 Febrero 2025
Found character that cannot start any token while scanning for the next token at line 86 column 1 -e LANG=en_US.UTF-8 Self-hosting	6	12395	7 Julio 2015
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	16	2383	26 Noviembre 2021
Failed to bootstrap on DO/Docker Fresh install Self-hosting server-resources	14	2958	7 Agosto 2015

El lanzador falla: línea 334: byte NULL ignorado

Temas relacionados