Closed MatthiasHertel closed 3 years ago
That's an odd error. It seems vagrant is trying to execute a bash command inside windows powershell, which will never work.
With the information you have provided I have no idea how to help.
I have the same error. Sorry for my Vagrant file - I'm quite new at this. I have been looking for solutions for this problem for a couple of weeks now.
This bit here seems interesting:
DEBUG host: Found cap: nfs_installed in linux INFO host: Execute capability: nfs_installed [#<Vagrant::Environment: /home/nout/git/ibm-ace-toolkit.vagrant/windows11>] (linux)
Looks like it thinks the guest is Linux, even though I explicitly told it (at least I think I did) it's Windoze.
@hoozemans, since you did not explicitly configure the vagrant synced folder type, it tried to use nfs, which does not normally work with a vanilla windows base vagrant box.
In a Ubuntu Linux host, instead of NFS, I normally use SMB. But, to use SMB in my Ubuntu host, I have to patch my vagrant installation. I do it as https://github.com/rgl/my-ubuntu-ansible-playbooks/blob/main/roles/vagrant/tasks/main.yml#L77-L120 which, among other things, requires the patch at https://github.com/rgl/my-ubuntu-ansible-playbooks/blob/main/roles/vagrant/files/vagrant-smb-9948.patch.
Also have a look at how vagrant synced_folder is configured at https://github.com/rgl/windows-domain-controller-vagrant/blob/master/Vagrantfile#L24-L26 (notice this is for the libvirt provider) and in https://github.com/rgl/windows-vagrant/blob/master/example/Vagrantfile.
HTH.
hi @rgl,
i am on host ubuntu , provider libvirt and i got the following error due running
vagrant up --provider=libvirt
what can i do?