Question
Vagrant, Windows, and DigitalOcean - anybody got this working?
- Posted on September 13, 2013
Asked by mbell
I’ve been trying (without success) to install the plugin vagrant-digitalocean in a Windows environment. I installed the latest version of Vagrant (1.3.1) However, when I try and install the plugin for digitalocean, the install fails:
$ vagrant plugin install vagrant-digitalocean Installing the ‘vagrant-digitalocean’ plugin. This can take a few minutes… C:/Tools2/Vagrant/embedded/lib/ruby/site_ruby/1.9.1/rubygems/installer.rb:556:in `rescue in block in build_extensions’: ERROR: Failed to build gem native extension. (Gem::Installer::ExtensionBuildError)
C:/Tools2/Vagrant/embedded/bin/ruby.exe extconf.rb
creating Makefile
make generating generator-i386-mingw32.def compiling generator.c linking shared-object json/ext/generator.so
make install
/usr/bin/install -c -m 0755 generator.so C:
/usr/bin/install -c -m 0755 generator.so .
/usr/bin/install: generator.so' and ./generator.so’ are the same file
make: *** [and] Error 1
Unfortunately I’m too new to Vagrant / DigialOcean to know where the problem lies. (I don’t seem to have any problem building the json gem in a pure ruby+devkit environment.
Having spent a few hours on this without any success, I’m about to abandon hope! Does anyone have a working installation? Does anybody recognize a common problem? Thanks.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
@David.Myers - Vagrant 1.2.7 has exactly the same problem - perhaps its breaking changes in the vagrant-digitalocean plugin. vagrant-aws installs OK, so perhaps EC2 is the answer for now.
Thanks everybody for the suggtetsions: <br> <br>@Kamal - Vagrant installs its own ruby-dev package. I have no problem compiling gems when I install the devkit with Ruby, but Vagrant prefers to use its own (apparently broken) one. <br>@Pablo of vDevices - yes, VirtualBox works fine. It appears to be an issue with compiling gems for the digitalocean provider - or possibly compiling gems for any provider. <br>@David.Myers - Thanks - I will try installing the older version of Vagrant and see whether that works. <br>@Pablo of vDevices - trying to avoid creating a Google/NSA account! Couldn’t see anything relevant in past postings there, and given that this problem is specific to DigitalOcean. <br> <br> <br>
The <a href=“https://groups.google.com/forum/?hl=en#!forum/vagrant-up”>Vagrant Google Group</a> is also a good place for help.