devopsgroup-io/vagrant-digitalocean

Provisioning a single file to droplet

jeusdi opened this issue · 1 comments

As you can see on bellow VagrantFile fragment, I'm provisioning a digital ocean droplet using shell and file provisioners:

config.vm.provision :file, :source => "docker.config", :destination => "/tmp/docker.config"
config.vm.provision :shell, :inline => "mkdir -p /home/core/.docker/; mv /tmp/docker.config /home/core/.docker/config.json", :privileged => true
config.vm.provision :shell, :inline => "mkdir -p /home/core/data/es; mkdir -p /home/core/data/mongo", :privileged => true

However vagrant is telling me:


 INFO warden: Calling OUT action: #<VagrantPlugins::DigitalOcean::Actions::CheckState:0x4713078>
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 1 hooks defined.
 INFO runner: Running action: machine_action_up #<Vagrant::Action::Warden:0x4499718>
 INFO warden: Calling IN action: #<Proc:0x5e74a50@C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/warden.rb:94 (lambda)>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Provision:0x44996d0>
 INFO provision: Checking provisioner sentinel file...
 INFO warden: Calling IN action: #<VagrantPlugins::DigitalOcean::Actions::ModifyProvisionPath:0x47c3748>
DEBUG ssh: Re-using SSH connection.
 INFO ssh: Execute: chown -R core  (sudo=true)
DEBUG ssh: stderr: chown: missing operand after 'core'
Try 'chown --help' for more information.

DEBUG ssh: Exit status: 1
DEBUG ssh: Re-using SSH connection.
 INFO ssh: Execute: chown -R core /tmp/vagrant-shell (sudo=true)
DEBUG ssh: stderr: chown: cannot access '/tmp/vagrant-shell': No such file or directory

What distribution is this?