Hello, I am unable to upgrade/rebuild my web_only container. The rebuild seems to fail when calling multisite migrate. A fresh install (no data, just my data.yml and web_only.yml files) yields the same error (the rebuild of the data container completes without error. Am I doing anything wrong or could it be a bug introduced in a recent upgrade? Alternatively, how could I circumvent this error? I don’t know the internals of the script but the scripts first says that /root/ is unwriteable, creates a tmp folder then seems to crash because mkdir fails in the /root/ directory. Many thanks! > Seeding theme and color schemes I, [2026-01-16T17:32:37.738763 #1] INFO -- : > cd /var/www/discourse && sudo -E -u discourse bundle exec rake multisite:migrate `/root` is not writable. Bundler will use `/tmp/bundler20260116-787-ovvxnu787' as your home directory temporarily. rake aborted! Discourse::Utils::CommandError: pnpm -C=frontend/asset-processor node build.js (Discourse::Utils::CommandError) WARN Issue while reading "/root/.npmrc". EACCES: permission denied, open '/root/.npmrc' WARN Issue while reading "/root/.config/pnpm/rc". EACCES: permission denied, open '/root/.config/pnpm/rc' ERROR EACCES: permission denied, mkdir '/root/.local/share/pnpm/.tools/pnpm/10.28.0_tmp_901' For help, run: pnpm help run /var/www/discourse/lib/discourse.rb:171:in `execute_command' /var/www/discourse/lib/discourse.rb:137:in `exec' /var/www/discourse/lib/discourse.rb:32:in `execute_command' /var/www/discourse/lib/asset_processor.rb:27:in `build_asset_processor' /var/www/discourse/lib/asset_processor.rb:31:in `build_production_asset_processor' /var/www/discourse/lib/tasks/assets.rake:155:in `block in ' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.1/exe/rake:27:in ` ' /usr/local/bin/bundle:25:in `load' /usr/local/bin/bundle:25:in ` ' Tasks: TOP => multisite:migrate => assets:precompile:asset_processor (See full trace by running task with --trace) FAILED -------------------- Pups::ExecError: cd /var/www/discourse && sudo -E -u discourse bundle exec rake multisite:migrate failed with return # Location of failure: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.4.0/lib/pups/exec_command.rb:138:in `spawn' exec failed with the params "cd /var/www/discourse && sudo -E -u discourse bundle exec rake multisite:migrate" bootstrap failed with exit code 1 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.

[изображение] Padoup-Padoup: sudo -E -u discourse bundle exec rake multisite:migrate this should be sudo -H -E -u discourse… (we should probably make set_home the default)

@david / @cvx could this be related to pnpm upgrade we did recently? :thinking:

It is unbelievable to me that I received the exact answer after… 25min :tada:! Many many thanks, the rebuild completed with success! Indeed, my web_only.yml contained the incorrect command. I remember following one of these tutorials: (that still contain the now-incorrect command ; not sure how to edit those posts). [изображение] Guidance on multi-site setup Self-hosting Hi everyone! I’ve been working on setting up a multi-site Discourse instance, and while I’ve made some progress, I’m running into a few roadblocks and could really use some guidance from someone. I’ve gone through the Multisite configuration with Docker guide, but I still have a few questions: Where can I find the “multisite.yml” file that’s mentioned? I don’t see it in my discourse/templates folder. Do I need to set up hooks for after_postgres even if I’m just using the standard volume and n… [изображение] Multisite configuration with Docker Self-Hosting warning While multisite is supported in the Discourse application, this is an advanced sysadmin setup. If you don’t know what you’re doing, do not set up multisite. The Discourse team is unable to provide multisite configuration support. If you wish to host multiple domains on a singled Docker setup, you’ll need a multisite configuration. Here are the basic building blocks for one. Understand hooks Multisite is a fairly advanced topic. Before attempting a multisite build, spend some time…

Yes it could, because I was in troubles when upgrade failed when wanting v10 and I had 9.something. So, I updated pnmp manually. And yes, I’m off topic because mine isn’t multisite and OP had different issue

[установка мультисайта] ошибка прав доступа pnpm при пересборке

Поддержка продукта Самостоятельное хостинг

zogstrip 16.Январь.2026 18:05:58 2

@david / @cvx, это может быть связано с недавним обновлением pnpm, которое мы сделали?

Various multisite installation questions

Тема		Ответов	Просм.
Build error: permission denied to create extension "vector" Product Support	3	364	14.08.2025
Pups::ExecError Self-hosting	13	1498	11.05.2023
'rebuild app' failed. looks like pnpm problem Self-hosting	2	239	04.03.2026
Upgrade to 2.8.0beta11 fails on multisite due to code review plugin Product Support	0	432	13.01.2022
Background worker "logical replication launcher" (PID 51) exited with exit code 1 Self-hosting	16	6934	17.09.2022

[установка мультисайта] ошибка прав доступа pnpm при пересборке

Связанные темы