On Monday, August 20, 2012 2:55:17 PM UTC+1, Andrew Sledge wrote:
This was a problem on my end. The postinstall.sh (using veewee) script ran some unsuspected changed on /etc/sudoers which was not formatted properly to handle vagrant using the NOPASSWD option.
On Sunday, August 19, 2012 12:31:59 PM UTC-4, Andrew Sledge wrote:
andrew@lin:~/work/personal-blog/vm$ vagrant up [default] VM already created. Booting if it's not already running... [default] Clearing any previously set forwarded ports... [default] Forwarding ports... [default] -- 22 => 2222 (adapter 1) [default] Creating shared folders metadata... [default] Clearing any previously set network interfaces... [default] Booting VM... [default] Waiting for VM to boot. This can take a few minutes. [default] VM booted and ready for use! [default] Mounting shared folders... [default] -- v-root: /vagrant The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed!