/home/vcap/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/irb/completion.rb:9:in `require': libreadline.so.5: cannot open shared object file: No such file or directory about ruby-buildpack

[dliebreich]

Can you please provide some more context for this error? What version of CloudFoundry are you using? Did this work in previous versions?

Why did you pick the version of libreadline.so that was in the php buildpack?

Thanks
@krishicks && @dliebreich
CF Community Pair

[pivotalfish]

@dliebreich this error surfaced when we tried to run rails c on a PWS cloud foundry instance (CF build 173)while in a tmate session.

We paired with @buddhistpirate (cf buildpacks team) and verified that this is a deficiency with the Ruby environment we use on Cloud Foundry. The buildpacks team informed us that the php buildpack version of libreadline has been compiled against the stemcell.

An alternative is to symlink the version of libreadline that's in /usr/lib: ln -s /usr/lib/libreadline.so ~/lib/libreadline.so.5.

~ @ckundo

[dliebreich]

@MarkKropf Would you like to weigh in on this?

Thanks
@krishicks && @dliebreich
CF Community Pair

[oppegard]

Just wanted to chime in that I had the same issue with the same use-case of trying rails c on PWS using a tmate session. Symlinking libreadline provided a workaround.

[jchesterpivotal]

A special-case workaround was baked into c992a82, which was bundled with 1.1.0.

The core problem is that we are ahead of Heroku in moving our base system images to later versions of Ubuntu.