Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Arch box fails to mount synced folder #14

Open
djhaskin987 opened this issue Oct 11, 2014 · 2 comments
Open

Arch box fails to mount synced folder #14

djhaskin987 opened this issue Oct 11, 2014 · 2 comments

Comments

@djhaskin987
Copy link

I'm using this box: http://cloud.terry.im/vagrant/archlinux-x86_64.box

I get this when I run vagrant up:

    default: /vagrant => /home/djhaskin987/Workspace/libgpg-error-git
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mkdir -p /vagrant

Stdout from the command:



Stderr from the command:


We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

sudo: no tty present and no askpass program specified

The synced folder does not show up:

$ vagrant ssh
Last login: Mon Aug 25 10:13:20 2014
vagrant@archlinux:~$ ls /
bin  boot  dev  etc  home  lib  lib64  lost+found  mnt  opt  proc  root  run  sbin  srv  sys  tmp  usr  var
@mdaffin
Copy link

mdaffin commented Oct 21, 2014

Seeing the same issue, it looks like sudo requires a password which is what is causing that error. You also get it if you run vagrant halt or vagrant reload

==> default: Attempting graceful shutdown of VM...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

shutdown -h now

Stdout from the command:



Stderr from the command:

sudo: no tty present and no askpass program specified

@marco-m
Copy link

marco-m commented Jun 28, 2017

Time to close this issue ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants