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.

[صورة] 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_only …

[صورة] 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 you’…

[صورة] 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 launcher …

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

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 …

الفاشل في الإطلاق: السطر 334: تم تجاهل بايت NULL

الدعم تثبيت

pfaffman (Jay Pfaffman) 4 أكتوبر 2024، 4:15م 2

يجب أن تكون قادرًا على إعادته للعمل باستخدام

./launcher start app

سيؤدي هذا إلى إعادة تشغيل الحاوية القديمة.

لا أعرف ما هي المشكلة الفعلية، ولكن قد تكون هناك مشكلة تراجعية.

الموضوع		الردود	مرات العرض
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 يونيو 2015
Launcher upgrade failing Self-hosting two-container	5	220	5 فبراير 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 يوليو 2015
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	16	2383	26 نوفمبر 2021
Failed to bootstrap on DO/Docker Fresh install Self-hosting server-resources	14	2958	7 أغسطس 2015

الفاشل في الإطلاق: السطر 334: تم تجاهل بايت NULL

الموضوعات ذات الصلة