Official Vagrant images for CentOS Linux 6.8 and CentOS Linux 7.2.1511 for x86_64 are now available for download, featuring updated packages to 30 October 2016, as well as the following user-visible changes:
microcode_ctl
centos/7
(this reduces boot time by ca. 5s)centos/7
image is based on CentOS Linux 7.2.1511, since CentOS Linux 7.3 is not available yet.config.vm.synced_folder ".", "/vagrant", type: "virtualbox"
We recommend using NFS instead of VirtualBox shared folders if possible.
config.vm.synced_folder ".", "/vagrant", disabled: true
to your Vagrantfile.
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
If you are using CentOS Linux on the host, we recommend installing Vagrant from SCL and using the libvirt images. In general, the Vagrant packages provided by your Linux distribution are preferable, since they usually backport fixes for some upstream bugs. If you are using Vagrant on other operating systems, please use Vagrant 1.8.6 (see Known issues, item 4).
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 ce12f84646efab28b007bdf16f3134686a23fa052f809c4600919561274051da --provider libvirt --box-version 1610.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.
Some of the optimisations in this release were inspired by the Vagrant images from Fedora Cloud and Debian Cloud.
We would also like to thank the following people (in alphabetical order):
You mention in Known Issue #2 the installation of the vagrant-vbguest plugin in order to use shared folders. This is important for synced folders. However, a Vagrantfile will also need the setting:
config.vm.synced_folder ".", "/vagrant", type: "virtualbox"
in order for VirtualBox directory sync to work.
I would suggest you add that to Known Issue #2 now and in future releases of these boxes.
Thank you.
$ vagrant up --provider vmware_fusion
...
The box you attempted to add doesn't match the provider you specified.
Provider expected: vmware_desktop
Provider of box: vmware_fusion
I'm working with vagrant and VirtualBox and I couldn't set an static IP addres. I don't know if it is related to the box or vagrant.
The kernel included in the box has been removed due to security issues and using the vagrant vbguest plugin to add guest additions no longer works without workarounds. We need an uodated box 🙁
This box doesn't seem to work with private_network and static IPs.
It seems to be because it doesn't disable predictable device naming ("net.ifnames=0 biosdevname=0").