rbenv: ruby: command not found
Solution 1
The complaint you get comes from rbenv. The fact that it's complaining shows that rbenv is set up and working.
Figure out what version of Ruby is needed to run the project. Either the project comes with a .ruby-version file in the root, or someone on the project will know and recommend that version to use.
If the version is not specified in a .ruby-version file, create the .ruby-version file in the project directory.
type
ruby -v
while in that directory. Is it OK? Then you have the version of Ruby installed that matches what your .ruby-version is asking for.If the last command was not OK, then type
rbenv install
.
Now that Ruby is installed, you need to run your program. I'm assuming it comes with a Rakefile.
install the bundler tool:
gem install bundler
.install the dependancies of the project:
bundle install
run your project using the exact versions of libraries it specifies:
bundle exec rails server
Solution 2
Try the following piece of code depending on the current version of rails that you have installed. In my case am using v2.3.3
rbenv global 2.3.3
Solution 3
Even setting global or local doesn't work if you haven't set this
echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.zshrc
echo 'eval "$(rbenv init -)"' >> ~/.zshrc
exec $SHELL
Solution 4
Even there is correct answer above, but it is not clear for my first check, so give a complete answer as a summarize based on z5h and Thengugi's answer. After setup and install ruby using rbenv as below (I installed 2.5.0):
rbenv install 2.5.0
You also need set it as the default version in your OS (CentOS for me):
rbenv global 2.5.0
Related videos on Youtube
Lawrence DeSouza
Updated on July 09, 2022Comments
-
Lawrence DeSouza almost 2 years
I am using rbenv with ruby version 1.9.1-p378 on the local dir.
Command ruby -v gives the following error:
rbenv: ruby: command not found The `ruby' command exists in these Ruby versions: 2.0.0-p353
Any clue why this happens? The bundle, rails commands do not work either.
Command rbenv versions :
* 1.9.1-p378 (set by /home/user/Desktop/r1/noko1/.ruby-version) 2.0.0-p353
-
Малъ Скрылевъ over 10 yearsAs you can see: the
ruby
app exists only in ruby 2.0.0 version, not in 1.9.1, just switch ruby to 2.0.0 -
Holger Just over 10 yearsYou really (really) don't want to use Ruby 1.9.1 as it is broken in multiple regards (encoding, rubygems, ...) and is generally not supported by anyone. You should use at least Ruby 1.9.2 if you want to use a 1.9 Ruby.
-
-
Lawrence DeSouza over 10 yearsI thought it was installed, see my edit, when i use rbenv versions
-
Conner over 10 yearsCan you share your
.rbenv-version
file in the desired directory? -
Lawrence DeSouza over 10 yearsIt just has the one line : 1.9.1-p378
-
Lawrence DeSouza over 10 yearsI'm trying to run an application that is giving me problems when i try to run it with 2.0.0. Something about rbconfig/config. That's why I'm trying to use it with 1.9.1. It is also using rails 2.3.2, which I gather from the gemfile of the app. However the rails command also does not work...
-
Conner over 10 yearsTake a look at stackoverflow.com/questions/10940736/…
-
Mark Bolusmjak over 10 yearsI have made step by step instructions. Let me know how it goes.
-
Lawrence DeSouza over 10 yearsYes! Thanks, [rbenv install] to get rubygems working - and then [gem install bundler] were big helps. However I had about 4 or 5 other things to fix including adding [gem rdoc] to the gemfile and installing a few other required gems like sqlite, etc, and finally downgrading the rubygems version again in order to use ./script/server start for rails 2.3.2 ; but after all that it WORKS! Thanks a bundle
-
justinpage over 9 yearsFor those still running into this issue, try and close your terminal first and trying again. Worked for me.
-
joe over 7 yearsAs someone who is completely unfamiliar with Ruby, this is the only thing that has worked for me,
-
randmin over 3 yearsI had to do this to tell rbenv what version of ruby to use. Insert whatever version you installed using rbenv install x.y[.z] (in my case 2.7.0). Now ruby -v works as expected