The update of discourse via ./launcher rebuild app fails with following output: x86_64 arch detected. Ensuring launcher is up to date Fetching origin Launcher is up-to-date Stopping old container + /usr/bin/docker stop -t 600 app app 2.0.20250129-0720: Pulling from discourse/base Digest: sha256:01b…

FYI, after migrating the (non-functional) install to the new hardware, I tried rebuilding just now again, and it run through smoothly.

I think perhaps this is where an error was encountered, perhaps in the pnpm package manager, but I don’t know the meaning of it: [imagen] Simon: I, [2025-02-23T14:01:10.746254 #1] INFO -- : Scope: all 17 workspace projects Lockfile is up to date, resolution step is skipped <E2><80><89>EINVAL<E…

The error is due to a mismatch between yarn and pnpm . The failure is specifically due to: EINVAL: invalid argument, rmdir '/var/www/discourse/app/assets/javascripts/dialog-holder/node_modules/.bin' Suggested Steps: Manually remove Node Modules: rm -rf node_modules app/assets/javascripts/*/node_…

I did as suggested, but the error unfortunately persists: ./launcher rebuild app x86_64 arch detected. WARNING: We are about to start downloading the Discourse base image This process may take anywhere between a few minutes to an hour, depending on your network speed Please be patient 2.0.202501…

Here’s the correct way to switch to PNPM as Discourse has transitioned to PNPM as its package manager , Ensure PNPM is installed: pnpm --version If it’s not installed, install it using npm: npm install -g pnpm Clean up old dependencies: rm -rf /var/www/discourse/node_modules rm -rf /var/www/disco…

Point 4 and git pull isn’t needed, because rebuild does it.

[imagen] Jakke Flemming: rebuild does it It does now, but it didn’t previously, so this is advice which works also for a very old installation.

Well, is out there any that old instances :man_shrugging: Not a big deal, though.

[imagen] Jakke Flemming: is out there any that old instances I mention it because when people get trouble upgrading, sometimes the reason is that they are a very long way behind. So it’s in exactly these threads that we should be as robust as we can.

[imagen] Simon: The update of discourse How old is your installation? Have you previously upgraded successfully? How old is your OS? Sometimes a problem is due to extensions which are no longer compatible, and the advice is to share a carefully censored version of your app.yml. I’m not sur…

Thanks for all the support, unfortunately it does not solve the problem. [imagen] Jahan Gagan: Ensure PNPM is installed: pnpm --version For new users maybe worth to add a: enter container (e.g., ./launcher enter app So I did. And pnp was already installed: root@vtdiscourse-app:/var/www/…

./launcher reconstruir error de la app: bootstrap falló con código de salida 234

Soporte

Ed_S (Ed S) 24 Febrero, 2025 09:24 7

Ahora lo hace, pero antes no, así que este es un consejo que también funciona para una instalación muy antigua.

2 Me gusta

Tema		Respuestas	Vistas
'rebuild app' failed. looks like pnpm problem Self-hosting	3	72	3 Abril 2026
Error when upgrading Discourse Self-hosting	12	362	11 Junio 2025
Launcher rebuild app Failure Self-hosting	7	692	6 Febrero 2024
Error while updating through launcher rebuild Self-hosting	3	538	16 Abril 2024
Update v3.4.0.beta3 +21 to v3.4.0.beta4 +37 fails, unable to create a directory Support	12	232	8 Mayo 2025

./launcher reconstruir error de la app: bootstrap falló con código de salida 234

Temas relacionados