We are pleased to announce new official Vagrant images of CentOS Linux 6.8 and CentOS Linux 7.3.1611 for x86_64, featuring updated packages to 28 February 2017.
config.vm.synced_folder ".", "/vagrant", type: "virtualbox"
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.
config.vm.synced_folder ".", "/vagrant", disabled: true
to their Vagrantfile.
Our automatic testing is running on a CentOS Linux 7 host, using Vagrant from SCL, with libvirt and VirtualBox 5.0.30 (without the VirtualBox Guest Additions) as providers. We strongly recommend using the libvirt provider when stability is required.
We also performed additional manual testing with Vagrant 1.9.0 on OS X 10.11.6, with VirtualBox 5.0.30.
The official images can be downloaded from Hashicorp’s Atlas. We provide images for libvirt-kvm, VirtualBox and VMware.
If you never used our images before:
$ vagrant box add centos/6 # for CentOS Linux 6 $ vagrant box add centos/7 # for CentOS Linux 7
Existing users can upgrade their images:
$ vagrant box update --box centos/6 $ vagrant box update --box centos/7
The SHA256 checksums of the images are signed with the CentOS 7 Official Signing Key. First, download and verify the checksum file:
$ curl http://cloud.centos.org/centos/7/vagrant/x86_64/images/sha256sum.txt.asc -o sha256sum.txt.asc $ gpg --verify sha256sum.txt.asc
If the check passed, you can use the corresponding checksum when downloading the image with Vagrant:
$ vagrant box add --checksum-type sha256 --checksum 48745c0f2dd4fbee366d830e3e333b637528ad936dd66ed5911df2adc02f46d7 --provider libvirt --box-version 1702.01 centos/7
Unfortunately, this is not possible with vagrant box update
.
If you encounter any unexpected issues with the Vagrant images, feel free to ask on the centos-devel mailing list, or via IRC, in #centos on Freenode.
We would like to thank Fabian Arrotin and Thomas Oulevey for their work on the build infrastructure.
We would also like to thank the following people (listed alphabetically):
Hi, I have the vmware_workstation provider but not the vwmare_fusion provider. I'm on Windows 10. I get this error when trying to use vmware_workstation:
==> my-worker1: Box 'centos/7' could not be found. Attempting to find and install...
my-worker1: Box Provider: vmware_desktop, vmware_fusion, vmware_workstation
my-worker1: Box Version: >= 0
==> my-worker1: Loading metadata for box 'centos/7'
my-worker1: URL: https://atlas.hashicorp.com/centos/7
==> my-worker1: Adding box 'centos/7' (v1702.01) for provider: vmware_desktop
my-worker1: Downloading: https://atlas.hashicorp.com/centos/boxes/7/versions/1702.01/providers/vmware_desktop.box
my-worker1:
The box you attempted to add doesn't match the provider you specified.
Provider expected: vmware_desktop
Provider of box: vmware_fusion
and I get this error when trying to use vmware_fusion:
The provider 'vmware_fusion' could not be found, but was requested to
back the machine 'my-worker1'. Please use a provider that exists.
I tried installing the vmware_fusion provider but it complains that I don't have a license for that. It's right, I only have a license for vmware_workstation.
Please advise. Thanks. Jeremy Hughes
How to use root account?