# Upgrade docker\_manager stuck - 2.2.0.beta4
**URL:** https://meta.discourse.org/t/upgrade-docker-manager-stuck-2-2-0-beta4/101656
**Category:** Support
**Created:** [November 9, 2018, 9:29am UTC](https://meta.discourse.org/t/upgrade-docker-manager-stuck-2-2-0-beta4/101656 "2018-11-09T09:29:25Z")
**Posts on this page:** 13
**Page:** 1
### Author:  [@znedw](https://meta.discourse.org/u/znedw)
#### Post date: [November 9, 2018, 9:29am UTC](https://meta.discourse.org/t/upgrade-docker-manager-stuck-2-2-0-beta4/101656/1 "2018-11-09T09:29:25Z")
Hi all,
I’ve just tried to upgrade from 2.2.0.beta3 to 2.2.0.beta4 however Docker Manager would not upgrade at all. The Docker Manager screen shows an empty console and ‘Upgrading…’. Pressing Reset Upgrade throws a JS error (see screenshot). There’s nothing in syslog. The machine has 4GB ram & 4GB swap. I ran ./launcher rebuild app and the upgrade worked but I’d love to keep using Docker Manager. Any ideas?
 !
Thanks,
Zach
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [November 9, 2018, 9:33am UTC](https://meta.discourse.org/t/upgrade-docker-manager-stuck-2-2-0-beta4/101656/2 "2018-11-09T09:33:24Z")
Hmm this is odd and I’ve never seen this before. Try rebuilding from the console
```plaintext
cd /var/discourse
./launcher rebuild
```
---
### Author:  [@znedw](https://meta.discourse.org/u/znedw)
#### Post date: [November 9, 2018, 9:35am UTC](https://meta.discourse.org/t/upgrade-docker-manager-stuck-2-2-0-beta4/101656/3 "2018-11-09T09:35:12Z")
Thanks for the quick reply, I tried ./launcher rebuild app initially and it worked fine going from beta3 to beta4, but Docker Manager still thinks it’s out of date and/or in the process of upgrading?
---
### Author:  [@znedw](https://meta.discourse.org/u/znedw)
#### Post date: [November 9, 2018, 11:19am UTC](https://meta.discourse.org/t/upgrade-docker-manager-stuck-2-2-0-beta4/101656/4 "2018-11-09T11:19:32Z")
I just noticed the commit hash for docker\_manager is different.
I ran
`
./launcher enter app
root@tarck-app:/var/www/discourse/plugins/docker_manager# git log --name-status HEAD^..HEAD
commit 61175ada7a1993647878c53320e9c6ffb1076dd2
`
So the repo is up to date but Discourse is showing an older hash (from Tuesday 18th Sep). I might try rebuild again and see what happens.
---
### Author:  [@znedw](https://meta.discourse.org/u/znedw)
#### Post date: [November 10, 2018, 8:33am UTC](https://meta.discourse.org/t/upgrade-docker-manager-stuck-2-2-0-beta4/101656/5 "2018-11-10T08:33:55Z")
Okay no luck with rebuilding the container again. Any ideas?
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [November 12, 2018, 5:42am UTC](https://meta.discourse.org/t/upgrade-docker-manager-stuck-2-2-0-beta4/101656/6 "2018-11-12T05:42:23Z")
Hmmm what is your app.yml, are you pulling docker manager plugin from a branch?
---
### Author:  [@znedw](https://meta.discourse.org/u/znedw)
#### Post date: [November 12, 2018, 8:25am UTC](https://meta.discourse.org/t/upgrade-docker-manager-stuck-2-2-0-beta4/101656/7 "2018-11-12T08:25:52Z")
```plaintext
hooks:
after_code:
- exec:
cd: $home/plugins
cmd:
- git clone https://github.com/discourse/docker_manager.git
- git clone https://github.com/davidtaylorhq/discourse-whos-online.git
- git clone https://github.com/znedw/discourse-poster-location.git
- git clone https://github.com/znedw/discourse-word-replace.git
```
master, I think?
```plaintext
root@tarck-app:/var/www/discourse/plugins/docker_manager# git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
```
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [November 12, 2018, 8:33am UTC](https://meta.discourse.org/t/upgrade-docker-manager-stuck-2-2-0-beta4/101656/8 "2018-11-12T08:33:16Z")
Are you 100% sure `rebuild` worked properly and did not error out somewhere?
---
### Author:  [@znedw](https://meta.discourse.org/u/znedw)
#### Post date: [November 12, 2018, 8:49am UTC](https://meta.discourse.org/t/upgrade-docker-manager-stuck-2-2-0-beta4/101656/9 "2018-11-12T08:49:37Z")
As far as I remember the rebuild went fine, are the rebuild logs persisted or just written to stdout? I can probably run the rebuild again and paste the output somewhere?
---
### Author:  [@jack2](https://meta.discourse.org/u/jack2)
#### Post date: [November 16, 2018, 11:11am UTC](https://meta.discourse.org/t/upgrade-docker-manager-stuck-2-2-0-beta4/101656/10 "2018-11-16T11:11:30Z")
I had the exact same issue: even after manual rebuild, `docker_manager` was stuck in “Currently Upgrading” state and the “Reset Upgrade” button was throwing an exception.
I fixed the issue by running this:
> [@Docker Manager "Reset Upgrade" Button is broken](https://meta.discourse.org/t/docker-manager-reset-upgrade-button-is-broken/86910/2):
>
> You could nuke all you upgrade keys I guess… ./launcher enter app rails c $redis.keys('upgrade:\*').each{|key| $redis.del key } I am confused though cause when you click on currently upgrading for assign it should allow you to reset it per: So perhaps this is failing and there is something in the logs?
---
### Author:  [@gigperformer](https://meta.discourse.org/u/gigperformer)
#### Post date: [November 16, 2018, 1:56pm UTC](https://meta.discourse.org/t/upgrade-docker-manager-stuck-2-2-0-beta4/101656/11 "2018-11-16T13:56:12Z")
I’m having exactly the same problem except that the process has gone part way through and then stopped. I realize it says, “This will take a while” but I started this yesterday.
```
== Seed from /var/www/discourse/db/fixtures/500_lounge_category.rb
== Seed from /var/www/discourse/db/fixtures/501_meta_category.rb
== Seed from /var/www/discourse/db/fixtures/502_staff_category.rb
== Seed from /var/www/discourse/db/fixtures/600_themes.rb
== Seed from /var/www/discourse/db/fixtures/990_settings.rb
== Seed from /var/www/discourse/db/fixtures/990_topics.rb
== Seed from /var/www/discourse/plugins/discourse-narrative-bot/db/fixtures/001_discobot.rb
== Seed from /var/www/discourse/plugins/discourse-narrative-bot/db/fixtures/002_badges.rb
***Bundling assets. This will take a while***
$ RUBY_GC_MALLOC_LIMIT_MAX=20971520 RUBY_GC_OLDMALLOC_LIMIT_MAX=20971520 RUBY_GC_HEAP_GROWTH_MAX_SLOTS=50000 RUBY_GC_HEAP_OLDOBJECT_LIMIT_FACTOR=0.9 bundle exec rake assets:precompile
This monkey patch is no longer required.
Purging temp files
Bundling assets
```
---
### Author:  [@znedw](https://meta.discourse.org/u/znedw)
#### Post date: [November 16, 2018, 9:35pm UTC](https://meta.discourse.org/t/upgrade-docker-manager-stuck-2-2-0-beta4/101656/12 "2018-11-16T21:35:59Z")
Thanks mate, this worked, can’t believe I didn’t see that post earlier. Upgraded docker\_manager to the latest and all is well.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [December 16, 2018, 9:36pm UTC](https://meta.discourse.org/t/upgrade-docker-manager-stuck-2-2-0-beta4/101656/13 "2018-12-16T21:36:00Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.