# Cannot upgrade from Docker Manager (missing gem)

**URL:** https://meta.discourse.org/t/cannot-upgrade-from-docker-manager-missing-gem/26035
**Category:** Support
**Tags:** docker
**Created:** [March 5, 2015, 5:12pm UTC](https://meta.discourse.org/t/cannot-upgrade-from-docker-manager-missing-gem/26035 "2015-03-05T17:12:31Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![frbn](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/frbn/32/115375_2.png) [@frbn](https://meta.discourse.org/u/frbn)
#### Post date: [March 5, 2015, 5:12pm UTC](https://meta.discourse.org/t/cannot-upgrade-from-docker-manager-missing-gem/26035/1 "2015-03-05T17:12:31Z")

</div>

I seem to be unable to use Docker Manager to upgrade my installation. It fails because it can’t find the gem 6to5-source, which according to [RubyGems.org](http://RubyGems.org) has been yanked.

This is the log:

```
$ cd /var/www/discourse && git fetch && git reset --hard HEAD@{upstream}
HEAD is now at a26853c try to work around caching bug in spec
********************************************************
 ***Please be patient, next steps might take a while***
 ********************************************************
$ bundle install --deployment --without test --without development
Fetching source index from https://rubygems.org/
Could not find 6to5-source-3.3.7 in any of the sources

```

Also, the manager does not seem to handle this well - my site is unavailable now. It probably should check that all gems are available before bundling, but that’s a different issue.

I managed to download the correct version of the gem from [RubyGems.org](http://RubyGems.org) manually, but is there a way to install it so the manager can upgrade?

Thanks in advance

**edit** : I figured maybe restarting the containers and reloading the upgrader would help, but that was a bad idea. Now the manager tells me everything’s up to date, which it most definitely isn’t.

**edit** : Can’t reach it at all now, this is the output of ./launcher logs:

```
ok: run: redis: (pid 30) 78s
ok: run: postgres: (pid 33) 78s
supervisor pid: 567 unicorn pid: 572
Could not find 6to5-source-3.3.7 in any of the sources
Run `bundle install` to install missing gems.
config/unicorn_launcher: line 44: kill: (572) - No such process
config/unicorn_launcher: line 10: kill: (572) - No such process
exiting

```

---

<div class="post-metadata">

### Author: ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [March 5, 2015, 5:35pm UTC](https://meta.discourse.org/t/cannot-upgrade-from-docker-manager-missing-gem/26035/2 "2015-03-05T17:35:56Z")

</div>

I’ll look into this ASAP.

I know the 6 to 5 project was renamed to babel but it would be really bad if they just yanked the old gem when projects depend on it.

---

<div class="post-metadata">

### Author: ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [March 5, 2015, 6:11pm UTC](https://meta.discourse.org/t/cannot-upgrade-from-docker-manager-missing-gem/26035/3 "2015-03-05T18:11:05Z")

</div>

Okay I’ve just pushed this to master:

[https://github.com/discourse/discourse/commit/4691fe35b3ac4e05d8b842903151c1ebfee08149](https://github.com/discourse/discourse/commit/4691fe35b3ac4e05d8b842903151c1ebfee08149)

You should be able to `./launcher rebuild` now.

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [March 5, 2015, 6:17pm UTC](https://meta.discourse.org/t/cannot-upgrade-from-docker-manager-missing-gem/26035/4 "2015-03-05T18:17:20Z")

</div>

Will this need to be backported onto beta and stable?

---

<div class="post-metadata">

### Author: ![frbn](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/frbn/32/115375_2.png) [@frbn](https://meta.discourse.org/u/frbn)
#### Post date: [March 5, 2015, 6:21pm UTC](https://meta.discourse.org/t/cannot-upgrade-from-docker-manager-missing-gem/26035/5 "2015-03-05T18:21:51Z")

</div>

```
Bundle complete! 92 Gemfile dependencies, 189 gems now installed.

```

Thank you so much, also for being so fast! I would assume that beta and stable deployment is still broken though? Not as horrible for me, as my site’s running on master, but I get that that’s not the recommended way 😉

Anyway, that’s a crappy move to just yank the old gem, and break deployment processes that depend on it.

---

<div class="post-metadata">

### Author: ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [March 5, 2015, 6:33pm UTC](https://meta.discourse.org/t/cannot-upgrade-from-docker-manager-missing-gem/26035/6 "2015-03-05T18:33:37Z")

</div>

Yes good call, I will backport it to beta/stable now.

edit: The fix is now in beta and stable branches too.

---

<div class="post-metadata">

### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [March 6, 2015, 11:10am UTC](https://meta.discourse.org/t/cannot-upgrade-from-docker-manager-missing-gem/26035/7 "2015-03-06T11:10:59Z")

</div>


