# Ruby 2.4.2 - failing after latest update

**URL:** <https://discuss.circleci.com/t/ruby-2-4-2-failing-after-latest-update/17855>\
**Category:** Programming Languages\
**Tags:** ruby, build-image\
**Created:** [November 3, 2017, 11:46am UTC](https://discuss.circleci.com/t/ruby-2-4-2-failing-after-latest-update/17855 "2017-11-03T11:46:06Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![david.wesmn](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/david.wesmn/32/7367_2.png) [@david.wesmn](https://discuss.circleci.com/u/david.wesmn)\
**Post date:** [November 3, 2017, 11:46am UTC](https://discuss.circleci.com/t/ruby-2-4-2-failing-after-latest-update/17855/1 "2017-11-03T11:46:06Z")

</div>

Hello!  
I ran my build 14 hours ago and it worked, 10 hours ago the ruby images were updated.

- Working: [https://circleci.com/gh/pensionsupplysning/web/17](https://circleci.com/gh/pensionsupplysning/web/17)
- Failing: [https://circleci.com/gh/pensionsupplysning/web/27](https://circleci.com/gh/pensionsupplysning/web/27)

For some reason, the right ruby gems cannot be accessed from inside rails commands, but they work when using SSH to connect.

Any clue on what have changed?

---

<div class="post-metadata">

**Author:** ![david.wesmn](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/david.wesmn/32/7367_2.png) [@david.wesmn](https://discuss.circleci.com/u/david.wesmn)\
**Post date:** [November 3, 2017, 12:04pm UTC](https://discuss.circleci.com/t/ruby-2-4-2-failing-after-latest-update/17855/2 "2017-11-03T12:04:36Z")

</div>

Might be related to Bundler and [this](https://github.com/bundler/bundler/issues/6144)

---

<div class="post-metadata">

**Author:** ![fernfernfern](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/fernfernfern/32/8596_2.png) [@fernfernfern](https://discuss.circleci.com/u/fernfernfern)\
**Post date:** [November 3, 2017, 12:38pm UTC](https://discuss.circleci.com/t/ruby-2-4-2-failing-after-latest-update/17855/3 "2017-11-03T12:38:44Z")

</div>

Hey @david.wesmn this can happen sometimes when we update our 1.0 images, and it’s related to your project cache. I’ve reset the cache for you, so your next build will take a bit longer to rebuild it. You should be good to go after that.

If anyone else is experiencing a similar issue please open a support ticket at [https://support.circleci.com](https://support.circleci.com)

---

<div class="post-metadata">

**Author:** ![david.wesmn](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/david.wesmn/32/7367_2.png) [@david.wesmn](https://discuss.circleci.com/u/david.wesmn)\
**Post date:** [November 3, 2017, 2:13pm UTC](https://discuss.circleci.com/t/ruby-2-4-2-failing-after-latest-update/17855/4 "2017-11-03T14:13:14Z")

</div>

Hello @fernfernfern.

I have tried clearing cache and running it without cache multiple times to no awail.

Should I open a support ticket instead?

---

<div class="post-metadata">

**Author:** ![fernfernfern](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/fernfernfern/32/8596_2.png) [@fernfernfern](https://discuss.circleci.com/u/fernfernfern)\
**Post date:** [November 3, 2017, 2:15pm UTC](https://discuss.circleci.com/t/ruby-2-4-2-failing-after-latest-update/17855/5 "2017-11-03T14:15:23Z")

</div>

@david.wesmn, yes please open a ticket. There may be something else at issue in your case here.

---

<div class="post-metadata">

**Author:** ![zzak](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/zzak/32/4233_2.png) [@zzak](https://discuss.circleci.com/u/zzak)\
**Post date:** [November 7, 2017, 8:44am UTC](https://discuss.circleci.com/t/ruby-2-4-2-failing-after-latest-update/17855/6 "2017-11-07T08:44:42Z")

</div>

@david.wesmn Does it help if you use `bin/rails test` instead of `bundle exec rails`?

---

<div class="post-metadata">

**Author:** ![david.wesmn](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/david.wesmn/32/7367_2.png) [@david.wesmn](https://discuss.circleci.com/u/david.wesmn)\
**Post date:** [November 7, 2017, 3:39pm UTC](https://discuss.circleci.com/t/ruby-2-4-2-failing-after-latest-update/17855/7 "2017-11-07T15:39:46Z")

</div>

I will try that if I have time, right now I kept bundler 1.16 but used `bundle install --system` instead of `bundle install --deploy`. But the caching is not as good then.

---

<div class="post-metadata">

**Author:** ![Eric](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/eric/32/2759_2.png) [@Eric](https://discuss.circleci.com/u/Eric)\
**Post date:** [November 7, 2017, 4:13pm UTC](https://discuss.circleci.com/t/ruby-2-4-2-failing-after-latest-update/17855/8 "2017-11-07T16:13:34Z")

</div>

Hi David,

Thank you for reporting this and for sharing that link to the bundler issue. I’ve reproduced this and confirmed it’s a problem with bundler 1.16.0 and [issue 6144](https://github.com/bundler/bundler/issues/6144).

To summarize for others, that issue affects `bundle install --deployment` and `bundle install --path <anything>`. We typically suggest `--path vendor/bundle`, but as long as this flag is used, bundler will follow a bad code path. This also only seems to affect certain programs and packages, ones that launch another Ruby process requiring the Bundler environment. I’ve seen this affect `rake test` and `rails test` because of the Spring loader, and `cucumber`.

A workaround is to install bundler 1.15.4 with:

```auto
sudo gem uninstall -x bundler
sudo gem install bundler --version 1.15.4

```

This will let you keep using `--deployment` or `--path vendor/bundle` for caching.

As for our convenience image, I’ll create an issue with the community Ruby image to see if I can get it fixed there. We can patch this in our Ruby convenience images, but I’d prefer to keep ours as close to the community images as possible.

---

<div class="post-metadata">

**Author:** ![david.wesmn](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/david.wesmn/32/7367_2.png) [@david.wesmn](https://discuss.circleci.com/u/david.wesmn)\
**Post date:** [November 7, 2017, 6:34pm UTC](https://discuss.circleci.com/t/ruby-2-4-2-failing-after-latest-update/17855/9 "2017-11-07T18:34:34Z")

</div>

Yes, bundler 1.15.4 probably works best. Hopefully there will be patches in bundler or e.g. spring.

---

<div class="post-metadata">

**Author:** ![david.wesmn](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/david.wesmn/32/7367_2.png) [@david.wesmn](https://discuss.circleci.com/u/david.wesmn)\
**Post date:** [November 8, 2017, 6:08am UTC](https://discuss.circleci.com/t/ruby-2-4-2-failing-after-latest-update/17855/10 "2017-11-08T06:08:04Z")

</div>

@Eric @zzak @fernfernfern  
The latest answer in the bundler thread seems to be on to something, saying the issue lies in the environment variables and spring.  
[https://github.com/bundler/bundler/issues/6144#issuecomment-342686828](https://github.com/bundler/bundler/issues/6144#issuecomment-342686828)

---

<div class="post-metadata">

**Author:** ![Eric](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/eric/32/2759_2.png) [@Eric](https://discuss.circleci.com/u/Eric)\
**Post date:** [November 8, 2017, 4:22pm UTC](https://discuss.circleci.com/t/ruby-2-4-2-failing-after-latest-update/17855/11 "2017-11-08T16:22:44Z")

</div>

Hi David,

Thanks for updating us. I think the issue is still Bundler 1.16.0 and not Spring-specific. The [suggested fix to Spring](https://github.com/bundler/bundler/issues/6144#issuecomment-342686828) he links to has a [failing test](https://travis-ci.org/rails/spring/jobs/298880237). In it, the failure messages are more dependency problems. Zak informed me that [rails/rails pinned Bundler to \< 1.16](https://github.com/rails/rails/commit/b106242f52272c4a5ced7a0e9d1dcb1b50542501) because they were getting failures on their master.

In addition to that issue, [this bundler issue regarding cucumber](https://github.com/bundler/bundler/issues/6147) and [this rubygems issue regarding bundler](https://github.com/rubygems/rubygems/issues/2055) produce similar errors. At least in the Rubygems issue, Spring isn’t involved.

Rubygems 2.7.2 fixed one person’s issue, but didn’t fix my `rails test` reproduction.

---

<div class="post-metadata">

**Author:** ![david.wesmn](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/david.wesmn/32/7367_2.png) [@david.wesmn](https://discuss.circleci.com/u/david.wesmn)\
**Post date:** [November 21, 2017, 10:34am UTC](https://discuss.circleci.com/t/ruby-2-4-2-failing-after-latest-update/17855/12 "2017-11-21T10:34:53Z")

</div>

Tried to switch back to `bundle install --deployment` now and it is working again:  
[https://circleci.com/gh/pensionsupplysning/web/89](https://circleci.com/gh/pensionsupplysning/web/89)

---

<div class="post-metadata">

**Author:** ![david.wesmn](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/david.wesmn/32/7367_2.png) [@david.wesmn](https://discuss.circleci.com/u/david.wesmn)\
**Post date:** [December 14, 2017, 11:37am UTC](https://discuss.circleci.com/t/ruby-2-4-2-failing-after-latest-update/17855/13 "2017-12-14T11:37:12Z")

</div>

I started having issues a while ago and still cannot use `bundle install --deployment`.

Did you figure this out @Eric?

---

<div class="post-metadata">

**Author:** ![Eric](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/eric/32/2759_2.png) [@Eric](https://discuss.circleci.com/u/Eric)\
**Post date:** [December 18, 2017, 8:45pm UTC](https://discuss.circleci.com/t/ruby-2-4-2-failing-after-latest-update/17855/14 "2017-12-18T20:45:33Z")

</div>

Hi David,

You saw a regression of this behavior because we rolled back a change to our Ruby images that uninstalled Bundler 1.16.0. That version of bundler wasn’t uninstalled fully because the upstream image installs it as a default gem, making it more difficult to uninstall.

For now, can you work around this issue by uninstalling bundler 1.16.0 as in this post:

[https://discuss.circleci.com/t/failed-to-invoke-bundler-on-circleci-2-0-with-circleci-ruby-2-4-2/18480/18](https://discuss.circleci.com/t/failed-to-invoke-bundler-on-circleci-2-0-with-circleci-ruby-2-4-2/18480/18)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\
**Post date:** [June 18, 2018, 11:32am UTC](https://discuss.circleci.com/t/ruby-2-4-2-failing-after-latest-update/17855/15 "2018-06-18T11:32:48Z")

</div>