Had some problems several months ago and ultimately I had to go back to
2.9.0.beta1 and simply could not update any further at that time.
Due to various extenuating circumstances I had to walk way from this project for some time and am just now able to get back to it. I did discover that the root problem turned out to be that the PostgreSQL database server had not been sufficiently and properly upgraded, this has now been resolved and it’s running at PostgresQL 14.x and Discourse is also running on this version of the database now.
Unfortunately when I tried to upgrade again via the normal web admin upgrade user interface it indicated that
fatal: HEAD does not point to a branch (full error here):
fatal: HEAD does not point to a branch Docker Manager: FAILED TO UPGRADE #<RuntimeError: RuntimeError> /var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:203:in `run' ...
I thought I could perhaps do a
/var/discourse/launcher rebuild app, but it did not end up working out either and only resulted in the same version starting back up, but I did notice the following output:
$ ./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.20220818-0047: Pulling from discourse/base 1efc276f4ff9: Pull complete 1b880e64942b: Pull complete 794f6dc9a2ff: Pull complete Digest: sha256:7734701087766821ffb2ddcef423754798bd345c2ac0d550131c6e6905c268e8 Status: Downloaded newer image for discourse/base:2.0.20220818-0047 docker.io/discourse/base:2.0.20220818-0047 ... I, [2022-09-13T02:09:12.828649 #1] INFO -- : Replacing # redis with sv start redis || exit 1 in /etc/service/unicorn/run I, [2022-09-13T02:09:12.829826 #1] INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/docker_manager.git Cloning into 'docker_manager'... I, [2022-09-13T02:09:13.957219 #1] INFO -- : I, [2022-09-13T02:09:13.958187 #1] INFO -- : > cd /var/www/discourse && git fetch --depth=1 origin tag v2.9.0.beta2 --no-tags From https://github.com/discourse/discourse * [new tag] v2.9.0.beta2 -> v2.9.0.beta2 I, [2022-09-13T02:09:18.214516 #1] INFO -- : I, [2022-09-13T02:09:18.215535 #1] INFO -- : > cd /var/www/discourse && git checkout v2.9.0.beta2 Note: switching to 'v2.9.0.beta2'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by switching back to a branch. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -c with the switch command. Example: git switch -c <new-branch-name> Or undo this operation with: git switch - Turn off this advice by setting config variable advice.detachedHead to false HEAD is now at 88a85843 FIX: Cooking custom emojis should not use a secure URL (#15929) I, [2022-09-13T02:09:19.557296 #1] INFO -- : ...
I ended up reverting these changes by restoring a backup and thought I should ask for some input here first as to how I could and should get Discourse properly reconnected to
main and start building again with the most recent beta - and then after I finally get this back up-to-date, I’d like to lock it into a stable release update in the future. I had used betas to resolve a problem I was having this past year, but this has been enough of an adventure for me.