Blank upgrade page after upgrading Docker Manager
Several users have reported a blank upgrade page after upgrading to the latest Docker Manager build (2.6.0.beta1). downey initially reported the issue, and Martin_Anonym experienced a site crash with a 521 error. Others, such as itsbhanusharma and Stanzilla, have also reported errors related to the Docker Manager plugin.
The issue was caused by a backward compatibility problem, which featheredtoast acknowledged and sam quickly fixed. The fix is available in the review fix-make-branch-hunting-backwards-compatible.
To recover from the issue, users can try running ./launcher rebuild app, which should get their site back up and running, as confirmed by featheredtoast. However, some users have reported that this solution does not work for them, as mentioned by EricGT.
Continuing the discussion from Blank upgrade page after updating docker manager to 2.0.0.beta10:
I just upgraded to build the latest docker manager and am now at build ( 3792ffa556 ) 2.6.0.beta1. My upgrade list is now blank. The Processes tab still works fine though.
Same here. After ./launcher rebuild app the whole Discourse is down .. Error 521
Already run multiple times ./launcher rebuild app but did not helped, not like in the mentioned Thread above.
I was on 2.6.0-beta1
Edit: after running it 3 more times, it came (after 10 min after finishing) back to life .. wtf?
I think this might be relevant,
We noticed a few errors in our discourse logs related to docker manager when our discourse went White Screen after upgrade.
NoMethodError (undefined method `find_compatible_git_resource' for Discourse:Module)
/var/www/discourse/plugins/docker_manager/lib/docker_manager/git_repo.rb:116:in `tracking_branch'
Message (2 copies reported)
NoMethodError (undefined method find_compatible_git_resource' for Discourse:Module) /var/www/discourse/plugins/docker_manager/lib/docker_manager/git_repo.rb:116:in tracking_branch’
Backtrace
/var/www/discourse/plugins/docker_manager/lib/docker_manager/git_repo.rb:116:in `tracking_branch'
/var/www/discourse/plugins/docker_manager/lib/docker_manager/git_repo.rb:11:in `initialize'
/var/www/discourse/plugins/docker_manager/lib/docker_manager/git_repo.rb:77:in `new'
/var/www/discourse/plugins/docker_manager/lib/docker_manager/git_repo.rb:77:in `find_all'
/var/www/discourse/plugins/docker_manager/app/controllers/docker_manager/admin_controller.rb:28:in `repos'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-6.0.3.1/lib/action_controller/metal/basic_implicit_render.rb:6:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-6.0.3.1/lib/abstract_controller/base.rb:195:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-6.0.3.1/lib/action_controller/metal/rendering.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack-6.0.3.1/lib/abstract_controller/callbacks.rb:42:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.1/lib/active_support/callbacks.rb:135:in `run_callbacks'
Env
HTTP HOSTS
@featheredtoast, is this your stuff?
Hmmm looks like something happened when I was rebasing this up - sorry about that. Will fix up shortly
I just pushed a fix, don’t worry about it 
https://review.discourse.org/t/fix-make-branch-hunting-backwards-compatible/13222?u=samsaffron
whoops wow, backwards compatability strikes again, the entire point of this feature. Irony. Good catch, thank you!
We got to make sure we backport the core support to beta and stable, cause otherwise we will be stuck for a long time before using this feature.
Thanks for the fix. Just to clarify, what’s the recovery strategy here for those affected?
./launcher rebuild {app-container} ?
That’s what we did but some are reporting this doesn’t work.
Correct, that should get your site back up and running 