I’m getting the following error when attempting to update. What is the best approach to work around this. BTW, we’ve not updated since 3.3.0.beta1-dev
** INCOMPATIBLE PLUGIN **
You are unable to start Discourse due to errors in the plugin at
/var/www/discourse/plugins/discourse-chat-integration
Please try removing this plugin and rebuilding again!
Docker Manager: FAILED TO UPGRADE
Best workaround? Remove the plugin for time being
Please share the related detailed error that will be earlier in the log.
I’m upgrading from the site. Only the docker_magager was selectable.
There may have been other log messages, but this is all I captured.
** INCOMPATIBLE PLUGIN **
You are unable to start Discourse due to errors in the plugin at
/var/www/discourse/plugins/discourse-chat-integration
Please try removing this plugin and rebuilding again!
Docker Manager: FAILED TO UPGRADE
#<RuntimeError: RuntimeError>
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:210:in `run'
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:108: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.2.0/gems/railties-7.0.8.1/lib/rails/commands/runner/runner_command.rb:43:in `load'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8.1/lib/rails/commands/runner/runner_command.rb:43:in `perform'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/thor-1.3.0/lib/thor/command.rb:28:in `run'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/thor-1.3.0/lib/thor/invocation.rb:127:in `invoke_command'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/thor-1.3.0/lib/thor.rb:527:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8.1/lib/rails/command/base.rb:87:in `perform'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8.1/lib/rails/command.rb:48:in `invoke'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8.1/lib/rails/commands.rb:18:in `<main>'
<internal:/usr/local/lib/ruby/site_ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:37:in `require'
<internal:/usr/local/lib/ruby/site_ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:37:in `require'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/bootsnap-1.18.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
bin/rails:18:in `<main>'
Spinning up 1 Unicorn worker(s) that were stopped initially
Only a command line upgrade is going to allow you to remove the plugin.
Swell! A Docker update is needed and we’re on Debian 9 with old repos.
./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.20231218-0429: Pulling from discourse/base
Digest: sha256:468f70b9bb4c6d0c6c2bbb3efc1a5e12d145eae57bdb6946b7fe5558beb52dc1
Status: Downloaded newer image for discourse/base:2.0.20231218-0429
docker.io/discourse/base:2.0.20231218-0429
WARNING: containers/app.yml file is world-readable. You can secure this file by running: chmod o-rwx containers/app.yml
Ensuring launcher is up to date
Fetching origin
remote: Enumerating objects: 587, done.
remote: Counting objects: 100% (586/586), done.
remote: Compressing objects: 100% (304/304), done.
remote: Total 587 (delta 324), reused 456 (delta 245), pack-reused 1 (from 1)
Receiving objects: 100% (587/587), 229.62 KiB | 0 bytes/s, done.
Resolving deltas: 100% (324/324), completed with 11 local objects.
From https://github.com/discourse/discourse_docker
7cc301e..928adfd main -> origin/main
* [new branch] build-log-level -> origin/build-log-level
* [new branch] consolidate_layers -> origin/consolidate_layers
* [new branch] docker-compose-generate -> origin/docker-compose-generate
* [new branch] generate-locales -> origin/generate-locales
* [new branch] start_release_stable_discourse_images -> origin/start_release_stable_discourse_images
Updating Launcher...
Updating 7cc301e..928adfd
Fast-forward
.github/workflows/build.yml | 168 +++++++++++++++++++++++++-----------------
.github/workflows/launcher_go.yml | 45 ++++++++++++
.gitignore | 1 +
... snip ...
create mode 100644 templates/postgres.15.template.yml
Launcher updated, restarting...
ERROR: Docker version 19.03.2 not supported, please upgrade to at least 20.10.0, or recommended 24.0.7
I’m going to build a Debian 12 server. What’s the best way to set up the new instance of Discourse given the existing database will be a older version?
That’s a sensible move and will save you time and risk
You should be fine pulling an older backup into a newer instance.
Unless I missed something, restore should just work.
You could also see Move a Discourse site to another VPS with rsync