We don't have access to any Windows computer, but some people reported that adding the following line to the Vagrantfile fixed the problem: Some people reported "could not resolve host" errors when running the centos/7 image for VirtualBox on Windows hosts.Please follow the detailed instructions in Installing open-vm-tools is not enough for enabling shared folders with Vagrant’s VMware provider.To their Vagrantfile, to prevent errors on "vagrant up". Windows users can either use SMB for synced folders, or disable the sync directory by adding the lineĬonfig.vm.synced_folder ".", "/vagrant", disabled: true Since the Guest Additions are missing, our images are preconfigured to use rsync for synced folders.We recommend using NFS instead of VirtualBox shared folders if possible you can also use the vagrant-sshfs plugin, which, unlike NFS, works on all operating systems. The VirtualBox Guest Additions are not preinstalled if you need them for shared folders, please install the vagrant-vbguest plugin and add the following line to your Vagrantfile:Ĭonfig.vm.synced_folder ".", "/vagrant", type: "virtualbox".All included packages have been updated to November 30th, 2018. We are pleased to announce new official Vagrant images of CentOS Linux 6.10 and CentOS Linux for x86_64. : We published new Vagrant images, v1811.02, fixing CentOS bug 15552 (wrong permissions on file /etc/sudoers.d/vagrant cause visudo -c to report an error, which can result in problems with Puppet). Updated CentOS Vagrant Images Available (v1811.01).
0 kommentar(er)
