Wait for NFS to be up

[pires]

kube-scheduler and kube-controller-manager won't start because of this.

Sep 02 09:46:01 master systemd[1]: Starting Export Hyperkube rkt image for usage in worker nodes...
Sep 02 09:46:01 master rkt[1290]: image: using image from local store for image name quay.io/coreos/hyperkube:v1.3.6_coreos.0
Sep 02 09:46:01 master rkt[1290]: sha512-d35a965c6a8bfcca7a00c476354e57dc
Sep 02 09:46:01 master rkt[1312]: export: unable to open output ACI file /vagrant/binaries/hyperkube_v1.3.6.aci: open /vagrant/binaries/hyperkube_v1.3.6.aci: no such file or directo
Sep 02 09:46:01 master systemd[1]: hyperkube-image-export.service: Main process exited, code=exited, status=1/FAILURE
Sep 02 09:46:01 master systemd[1]: Failed to start Export Hyperkube rkt image for usage in worker nodes.
Sep 02 09:46:01 master systemd[1]: hyperkube-image-export.service: Unit entered failed state.
Sep 02 09:46:01 master systemd[1]: hyperkube-image-export.service: Failed with result 'exit-code'.

[pires]

As a workaround, use sudo vagrant up for now.

[elderbig]

I meet this also. I run this repo on Centos7 x86_64 with VirtualBox 5.2 and Vagrant 2.1.1 when I sudo vagrant up,another error appears:

The VirtualBox VM was created with a user that doesn't match the current user running Vagrant. VirtualBox requires that the same user be used to manage the VM that was created. Please re-run Vagrant with that user. This is not a Vagrant issue.

The UID used to create the VM was: 1000 Your UID is: 0