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 30 March 2017 and the following changes:
- The VMware images now use the paravirtualized SCSI controller (the kernel module for the LSILogic controller has been deprecated upstream).
- The VMware images now specify vmware_desktop, allowing them to work with both VMware Fusion and VMware Workstation
- 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:
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.
- Since the Guest Additions are missing, our images are preconfigured to use rsync for synced folders. Windows users can either use SMB for synced folders, or disable the sync directory by adding the line
config.vm.synced_folder ".", "/vagrant", disabled: true
to their Vagrantfile.
- Vagrant 1.8.5 is unable to create new CentOS Linux boxes due to Vagrant bug #7610
- Vagrant 1.8.7 is unable to download or update boxes due to Vagrant bug #7969.
- Vagrant 1.9.1 broke private networking, see Vagrant bug #8166
- Vagrant 1.9.3 doesn't work with SMB sync due to Vagrant bug #8404
- Installing open-vm-tools is not enough for enabling shared folders with Vagrant’s VMware provider. Please follow the detailed instructions in https://github.com/mvermaes/centos-vmware-tools (updated for this release).
Recommended Setup on the Host
Our automatic testing is running on a CentOS Linux 7 host, using Vagrant 1.8.1 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.3 on OS X 10.11.6, with VirtualBox 5.1.18.
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
Verifying the integrity of the images
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 82bbed14c34fdd8fd3cb617b0e8c0f154ebd4d1388f45de3335b2cdf791e5fed --provider libvirt --box-version 1703.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):
- Graham Mainwaring, for helping with tests and validations
- Michael Vermaes, for testing our official images, as well as for writing the detailed guide to using them with VMware Fusion Pro and VMware Workstation Pro.
9 thoughts on "Updated CentOS Vagrant Images Available (v1703.01)"
Would be great if there were official CentOS vagrant images for KVM.
The images for KVM are the libvirt images, and have been available from the very beginning.
Is `rsync__auto` meant to work or not? I've never gotten it to yet.
That's probably dependent on the host OS (if it supports filesystem events), not on the Vagrant images themselves. Try to specify explicitly whether polling should be used or not. https://www.vagrantup.com/docs/cli/rsync-auto.html
Is it possible to include a Hyper-V Provider for CentOs Vagrant in the future for us Windows Folks? Unable to have both Hyper-V & Virtual box installed on the same host and Docker for Windows is natively Hyper-V nowadays.
This is work in progress since October 2016, I think - hopefully soon.
thanks,synced_folder with vagrant-vbguest is work on VirtualBox 5.1.18, not work in VirtualBox 5.1.20,host os windows7
It's probably best to report such regressions to the VirtualBox developers, after searching their bug tracker and forums if the problem isn't already known. In this case, it was already reported and there's even a test build of the Guest Additions containing the fix. Please see https://www.virtualbox.org/ticket/16670.
autorelabel doesn't work on VirtualBox. I opened a bug at https://bugs.centos.org/view.php?id=13213 and you can find a demo Vagrantfile at https://gist.github.com/schlomo/b532ba9bca87ea40d922d90e62b7338c
Discovered during my work on Relax-and-Recover workshop, see https://github.com/rear/rear-workshop-osbconf-2016/issues/4