Question

DigitalOcean as Vagrant Provider from Windows

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: #VagrantPlugins::DigitalOcean::Actions::SyncFolders:0x364f590 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.


Submit an answer

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!

Sign In or Sign Up to Answer

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.

I was having similar problems and fixed it by installing the older 1.2.7 version of Vagrant

Try installing the ruby-dev package – does that fix it?

I’m having no luck at all with Vagrant 1.3.1. <br>Installed Vagrant using the installer. Appears to work OK for VirtualBox. <br>But the external compiler code appears to be broken so I get: <br> <br>mbell@dogbert /cygdrive/c/temp/vagrant <br>$ vagrant plugin install vagrant-digitalocean <br>Installing the ‘vagrant-digitalocean’ plugin. This can take a few minutes… <br>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) <br> <br> C:/Tools2/Vagrant/embedded/bin/ruby.exe extconf.rb <br>creating Makefile <br> <br>make <br>generating generator-i386-mingw32.def <br>compiling generator.c <br>linking shared-object json/ext/generator.so <br> <br>make install <br>/usr/bin/install -c -m 0755 generator.so C: <br>/usr/bin/install -c -m 0755 generator.so . <br>/usr/bin/install: generator.so’ and `./generator.so’ are the same file <br>make: *** [and] Error 1 <br> <br>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. <br> <br>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? <br>