Running "Bundle Install" Fails and Asks Me to Run "Bundle Install"

Running bundle install fails and asks me to run bundle install

OK guess I fixed it..

For the gems that running bundle install complained about when run from inside the app directory, I installed them by going outside the app directory and doing sudo gem install [gem] one by one. Doing bundle install --gemfile=myApp/Gemfile also installed a couple of the missing gems.

I have no idea why I wasn't able to just run bundle install from inside the app directory...lame.

Bundle install fails, Gem install succeeds

I fixed this after many hours of struggle, by noticing that on the GitHub Pages repo there's a note that says

Important: Make sure you have Bundler > v1.14 by running gem update bundler in your terminal before following the next steps.

I have no idea why this mattered but I removed my ruby packages from Ubuntu and reinstalled them, then installed bundler with rubygems, which gave me a newer version:


sudo apt-get remove ruby
sudo apt-get install ruby ruby-dev
sudo gem install bundler
bundler --version


If anyone knows why I needed that version of bundler, or how I should have diagnosed this faster, I'd be interested to hear it. I'm not new to programming but I'm new to Ruby.

bundle install fails even though bundler-1.1.3 is installed

Try to remove your Gemfile.lock. Then run bundle check and see the output. It may ask you to run bundle install again.

Bundle install is not working

It's a connectivity issue.

I solved it through hideMe VPN. It is used to bypass blocked websites or for servers down only for a particular user.

Now everything seems to work just fine.

Error while Bundle install

First add the gem gem 'libv8', '~> 3.16', '>= 3.16.14.7' into the gem file or run gem install libv8 -v 3.16.14.7.

Once you have installed or added the gen, run bundle install.

the gem file will be added successfully.

running bundle install command is failure

system creates a subprocess and then exits. The subprocess changed directory and then finished, but your script still thinks it's in whatever working directory the process thinks it's in.

If you want to change the working directory of the process running the script, use Dir.chdir().

---

Related Topics