| Summary | Provides basic monitoring and update facilities to Discourse instances hosted using our Docker template: GitHub - discourse/discourse_docker: A Docker image for Discourse | |
| Repository Link | GitHub - discourse/docker_manager: Plugin for use with discourse docker image | |
| Install Guide | This plugin is included by default in all standard installs |
为了增加可见性,在此处交叉链接:![]()
ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL 命令被 SIGKILL (强制终止) 杀死:ember build -prod Docker Manager: 升级失败
每次更新尝试后…
请发布完整的日志?谢谢!
我认为我在没有交换空间的情况下遇到了这个问题,并通过添加交换空间解决了它。
编辑,这证实了我的建议:
我可能会尝试一下,即使我的机器有 4GB 的可用内存
如果真的花费太长时间,会不会是因为 Cloudflare?
我已经更新了我的另一个服务器,看看这个错误是否会再次发生,我会发布一些日志。
还有日志的一部分……
== 20250313045010 AddIndexToUsersIpAddress: migrating =========================
-- remove_index(:users, :ip_address, {:algorithm=>:concurrently, :name=>"idx_users_ip_address", :if_exists=>true})
-> 0.0310s
-- add_index(:users, :ip_address, {:algorithm=>:concurrently, :name=>"idx_users_ip_address"})
-> 0.0161s
== 20250313045010 AddIndexToUsersIpAddress: migrated (0.0492s) ===============
Seeding default
*** Bundling assets. This will take a while ***
$ bundle exec rake themes:update assets:precompile
Updating themes with concurrency: 10
Node.js heap_size_limit (2010.75) is less than 2048MB. Setting --max-old-space-size=2048 and CHEAP_SOURCE_MAPS=1
Building
Environment: production
The setting 'staticAddonTrees' will default to true in the next version of Embroider and can't be turned off. To prepare for this you should set 'staticAddonTrees: true' in your Embroider config.
The setting 'staticAddonTestSupportTrees' will default to true in the next version of Embroider and can't be turned off. To prepare for this you should set 'staticAddonTestSupportTrees: true' in your Embroider config.
building...
...[ConfigLoader]
...[Babel: discourse-widget-hbs > applyPatches]
...[Babel: @embroider/macros > applyPatches]
...[Babel: ember-tracked-storage-polyfill > applyPatches]
...[Babel: pretty-text > applyPatches]
...[Babel: @ember/legacy-built-in-components > applyPatches]
...[Babel: ember-source > applyPatches]
[BABEL] Note: The code generator has deoptimised the styling of /var/www/discourse/app/assets/javascripts/discourse/ember/ember-template-compiler.js as it exceeds the max of 500KB.
[BABEL] Note: The code generator has deoptimised the styling of /var/www/discourse/app/assets/javascripts/discourse/ember/ember.js as it exceeds the max of 500KB.
...[Babel: ember-source > applyPatches]
...[Babel: @glimmer/component > applyPatches]
...[Babel: @ember/render-modifiers > applyPatches]
...[Babel: @ember/test-waiters > applyPatches]
...[Babel: dialog-holder > applyPatches]
...[Babel: ember-this-fallback > applyPatches]
...[Babel: ember-buffered-proxy > applyPatches]
...[Babel: ember-cache-primitive-polyfill > applyPatches]
...[Babel: float-kit > applyPatches]
...[Babel: select-kit > applyPatches]
...[@embroider/compat/app]
...[@embroider/webpack]
...[@embroider/webpack]
...[@embroider/webpack]
...[@embroider/webpack]
...[@embroider/webpack]
...[@embroider/webpack]
...[@embroider/webpack]
...[@embroider/webpack]
...[@embroider/webpack]
...[@embroider/webpack]
...[@embroider/webpack]
...[@embroider/webpack]
...[@embroider/webpack]
...[@embroider/webpack]
undefined
ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL Command was killed with SIGKILL (Forced termination): ember build -prod
Docker Manager: FAILED TO UPGRADE
#<RuntimeError: RuntimeError>
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:211:in `run'
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:112:in `upgrade'
/var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:19:in `block in <main>'
/var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:6:in `fork'
/var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:6:in `<main>'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/commands/runner/runner_command.rb:44:in `load'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/commands/runner/runner_command.rb:44:in `block in perform'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/execution_wrapper.rb:91:in `wrap'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/commands/runner/runner_command.rb:70:in `conditional_executor'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/commands/runner/runner_command.rb:43:in `perform'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/thor-1.3.2/lib/thor/command.rb:28:in `run'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/thor-1.3.2/lib/thor/invocation.rb:127:in `invoke_command'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/command/base.rb:178:in `invoke_command'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/thor-1.3.2/lib/thor.rb:538:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/command/base.rb:73:in `perform'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/command.rb:71:in `block in invoke'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/command.rb:149:in `with_argv'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/command.rb:69:in `invoke'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/commands.rb:18:in `<main>'
/usr/local/lib/ruby/3.3.0/bundled_gems.rb:69:in `require'
/usr/local/lib/ruby/3.3.0/bundled_gems.rb:69:in `block (2 levels) in replace_require'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/bootsnap-1.18.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
bin/rails:18:in `<main>'
Spinning up 7 Unicorn worker(s) that were stopped initially
这个错误是因为 Ubuntu 版本引起的吗?
问题出在服务器上。我的第三台服务器没有问题,但另外两台服务器似乎显示有 4GB 内存,但实际上并没有那么多……
如果我理解正确的话,通过 Docker Manager 为自托管实例更新插件似乎相当方便。
我安装了这个插件,如何访问帖子中看到的带有插件选项卡的视图?这是更新选项卡吗?我可以看到插件列在“更新”选项卡下,所以我想我安装正确了。
更新选项卡应该看起来和以前不一样吗?
或者也许我只是有点笨,安装了我已经有的东西。我以为安装了这个之后安装插件会更容易,但我认为我仍然需要通过 SSH 来安装。
谢谢,我误以为这是我已有的额外的东西。
Web 上的升级失败了。我的 Discourse 版本是 3.5.0.beta1。
补充:
在我的服务器命令中尝试 ./launcher rebuild app 后,我遇到了相同的错误。
Discourse::ScssError: Error: @use 规则必须写在任何其他规则之前。(Discourse::ScssError)
您需要运行
./launcher rebuild app
运行 ./launcher rebuild app 时也出现了这个错误。我需要将我的 Discourse 版本升级到最新吗?
我找到原因了。这是因为 discourse-data-explorer 插件已更新,无法在 v3.5.0-beta1 上构建。抱歉~ ![]()
各位,请检查 Discourse 核心自带的插件列表。如果您尝试安装新版本核心自带的插件,将会遇到安装问题。请从您的 /var/discourse/containers/app.yml 文件中删除这些行或注释掉这些行。
请查看此链接了解插件:
祝您好运。
只是好奇,为什么这个插件现在不是核心存储库的一部分,这不被认为是核心功能吗?
因为它仅适用于自托管网站。



