p0deje / vagrant-vultr

Vultr provider for Vagrant
MIT License
46 stars 16 forks source link

Debian provisioning failed: no sudo #10

Open mactkg opened 7 years ago

mactkg commented 7 years ago

Problem

Vagrant will install rsync after a VM booted but it failed because debian 8 image on Vultr don't have sudo command.

... after booted the VM and vagrant detected it is debian

==> default: Installing rsync to the VM...
DEBUG ssh: Checking whether SSH is ready...
DEBUG ssh: Re-using SSH connection.
 INFO ssh: SSH is ready!
DEBUG ssh: Re-using SSH connection.
 INFO ssh: Execute:  (sudo=false)
DEBUG ssh: stderr: stdin: is not a tty

DEBUG ssh: stderr: **-vagrant-ssh
DEBUG ssh: Exit status: 0
DEBUG guest: Searching for cap: rsync_install
DEBUG guest: Checking in: debian
DEBUG guest: Found cap: rsync_install in debian
 INFO guest: Execute capability: rsync_install [#<Vagrant::Machine: default (VagrantPlugins::Vultr::Provider)>] (debian)
DEBUG ssh: Re-using SSH connection.
 INFO ssh: Execute:             apt-get -yqq update
            apt-get -yqq install rsync
 (sudo=true)
DEBUG ssh: stderr: bash: sudo: command not found

DEBUG ssh: Exit status: 127
ERROR warden: Error occurred: The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

            apt-get -yqq update
            apt-get -yqq install rsync

how to solve

vagrant-digitalocean had same issue but it solved, so we can fix same ways. However, I think this issue may also be fixed improving provisioning code in Vagrant... How do you think?

Anyway, I try dealing with this issue next weekend.

p0deje commented 7 years ago

I no longer actively maintain this plugin, so if you'd like to become a maintainer and fix this (along with few other unresolved issues), I'm more than happy to give you full access.