DigitalOcean as Vagrant Provider from Windows

August 15, 2013 3.2k views
Hi, Has anyone had any luck running DigitalOcean as Vagrant Provider from Windows? Appears an error occurs just after rsync triggers.... INFO warden: Calling action: # INFO interface: info: Rsyncing folder: C:/digiOceanTest/ => /vagrant... [default] Rsyncing folder: C:/digiOceanTest/ => /vagrant... INFO ssh: Execute: mkdir -p /vagrant (sudo=true) INFO ssh: Execute: chown -R root /vagrant (sudo=true) INFO subprocess: Starting process: ["rsync", "--verbose", "--archive", "-z", "--delete", "-e", "ssh -p 22 -o StrictHostKeyChecking=no -i 'C:/digiOcean_rsa'", "C:/digiOceanTest/", "root@XXX.XXX.XXX.XXX:/vagrant"] ERROR warden: Error occurred: Unknown error (Windows says "The operation completed successfully.", but it did not.) INFO warden: Beginning recovery process... INFO warden: Recovery complete. .... My guess would be an issue with path format, but wondered if anyone has encountered this before? Thanks, A.
4 Answers
What process did you follow (or, what steps did you take) to reach the point where you encountered these errors?
I'm having no luck at all with Vagrant 1.3.1.
Installed Vagrant using the installer. Appears to work OK for VirtualBox.
But the external compiler code appears to be broken so I get:

mbell@dogbert /cygdrive/c/temp/vagrant
$ 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

generating generator-i386-mingw32.def
compiling generator.c
linking shared-object json/ext/

make install
/usr/bin/install -c -m 0755 C:
/usr/bin/install -c -m 0755 .
/usr/bin/install: `' and `./' are the same file
make: *** [and] Error 1

Unfortunately I'm sufficiently new to this area to not be sure whether this is an error in the vagrant-digitalocean plugin or the as-provided Vagrant 1.3.1 windows installer.

and having spent several hours trying to find a work-around, I'm preparing to give up on the idea of using Vagrant to provision a test machine on DigitalOcean. Anybody got any suggestions?
Try installing the ruby-dev package -- does that fix it?
I was having similar problems and fixed it by installing the older 1.2.7 version of Vagrant
Have another answer? Share your knowledge.