# Discourse Upgrade Failed With Ruby 2.4 or above required

**URL:** <https://meta.discourse.org/t/discourse-upgrade-failed-with-ruby-2-4-or-above-required/92782>\
**Category:** Self-hosting\
**Created:** [July 20, 2018, 7:47am UTC](https://meta.discourse.org/t/discourse-upgrade-failed-with-ruby-2-4-or-above-required/92782 "2018-07-20T07:47:18Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![justme](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@justme](https://meta.discourse.org/u/justme)\
**Post date:** [July 20, 2018, 5:44pm UTC](https://meta.discourse.org/t/discourse-upgrade-failed-with-ruby-2-4-or-above-required/92782/5 "2018-07-20T17:44:29Z")

</div>

That’s what I ended up doing. Started in the forum with “don’t have to login to the machine” upgrade, got docker upgrade ok there, went to update discourse and got the Ruby error. No idea if it was talking about needing it in the container or outside of the container. Took a shot that it was inside the container. After that didn’t work went to do the app rebuild, told me the docker container was at like 1.9.1 and need to be at 17 something tried the apt lxc-docker update, that didn’t work, finally found the command using wget and that got docker updated to 18 something. Then the rebuild was able to start and finished successfully with no errors. Forum was back online. So ya, the update was done through the command line after the preferred method blew up and at 4am in the morning I wasn’t going to complain.

---

_[View the full topic](https://meta.discourse.org/t/discourse-upgrade-failed-with-ruby-2-4-or-above-required/92782)._