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

vagrant up broken by nfs #118

Open
jpgreth opened this issue Mar 16, 2018 · 1 comment
Open

vagrant up broken by nfs #118

jpgreth opened this issue Mar 16, 2018 · 1 comment

Comments

@jpgreth
Copy link

jpgreth commented Mar 16, 2018

I have an Ubuntu 16.04 Host with Vagrant 2.0.3, Virtual Box 5.2.8 and nfs-common nfs-kernel-server installed.

I cloned according to the manual with git clone --recursive --config core.autocrlf=false https://github.com/webdevops/vagrant-development.git devvm

When i now do avagrant up, i get:

jafix@Snoeten:~/vagrant/devvm$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'bento/ubuntu-16.04'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'bento/ubuntu-16.04' is up to date...
==> default: Setting the name of the VM: devvm_default_1521234381169_59232
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: 
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default: 
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Configuring and enabling network interfaces...
==> default: Exporting NFS shared folders...
==> default: Preparing to edit /etc/exports. Administrator privileges will be required...
==> default: Mounting NFS shared folders...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mount -o vers=3,udp 192.168.56.1:/home/jafix /home/jafix

Stdout from the command:

Stderr from the command:

mount.nfs: Connection timed out

What could be wrong here?

vagrant up --debug &> vagrant.log can be found here: https://gist.github.com/jgreth/76f994f5ff6ea49606e9b4410f7270b6

@josefglatz
Copy link
Member

Did you tried a few times times? My experience was, that with VirtualBox is everything "buggy"

But from beside of that: is it a real benefit to run a docker host within VirtualBox on Ubuntu itself?

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

No branches or pull requests

2 participants