Seven.CentOS.org

UPDATE 2016-09-08: Due to additional checks, we had to retire v1608.01 from Atlas and release it again as v1608.02. The two versions are identical.

Official Vagrant images for CentOS Linux 6 and CentOS Linux 7 for x86_64 are now available for download, featuring updated packages to 31 August 2016, as well as a new image for VMware Fusion.

Known Issues

1. The VirtualBox Guest Additions are not preinstalled; if you need them for shared folders, please install the vagrant-vbguest plugin. We recommend using NFS instead of VirtualBox shared folders if possible.
2. 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 the Vagrantfile.
3. Vagrant 1.8.5 is unable to create new Linux boxes due to Vagrant bug #7610. You can use Vagrant 1.8.4 until version 1.8.6 is released.

Downloads

The official images can be downloaded from Hashicorp’s Atlas. We provide images for libvirt, 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 by:

$ vagrant box update --box centos/6
$ vagrant box update --box centos/7

Checksums

The downloaded images should have the following SHA256 checksums:

914ab02db12f2d19f71dbd3c6cb171dff683893443e26f2f03160491945366dc  CentOS-6-x86_64-Vagrant-1608_01.LibVirt.box
5391ea7bdafafe8d8df58b8405d81cafdcd0b8273c18cdd37133dcf1cb329a0b  CentOS-6-x86_64-Vagrant-1608_01.VirtualBox.box
4d6a5906ada93a5228f62671f7c97bed0ae3c961df108c25ceee278a8d9d17d2  CentOS-6-x86_64-Vagrant-1608_01.VMwareFusion.box
2916442968486a41315cb93d35fbbaeaf72e200f051f4996b5766649b8c3a325  CentOS-7-x86_64-Vagrant-1608_01.LibVirt.box
415b79487cdb7e0246ef93585de08d2063b1e7b85ff5666f60de5cb96a4a027c  CentOS-7-x86_64-Vagrant-1608_01.VirtualBox.box
44d26155e89fa5d74994167489bd66da4187b3da02ac3a063f0b26cfab965baf  CentOS-7-x86_64-Vagrant-1608_01.VMwareFusion.box

Vagrant has the ability to verify that the downloaded image has a specific checksum, e.g.

$ vagrant box add --checksum-type sha256 --checksum 2916442968486a41315cb93d35fbbaeaf72e200f051f4996b5766649b8c3a325 --provider libvirt centos/7

Unfortunately, this is not possible with vagrant box update.

Feedback

If you encounter any unexpected issues with the Vagrant images, feel free to ask on the centos-devel mailing list, or in #centos-devel on Freenode.

Official Vagrant images for CentOS Linux 6 and CentOS Linux 7 for x86_64 are now available for download, featuring updated packages to 28 July 2016 and the following improvements:

• Follow upstream Vagrant recommendations:
  • The default Vagrant sync directory is set to /vagrant
  • sshd DNS lookups are disabled by default
  • The root password is set to vagrant
• The GRUB timeout is set to just 1 second, to decrease the boot time
• [security]: sshd password authentication is now disabled (the vagrant user is configured with the publicly-known password vagrant and passwordless sudo, making it trivial for third-parties to gain administrative access via ssh if password authentication is enabled). You can still login as root or vagrant by entering the password on the console, if needed. We recommend re-creating all Vagrant boxes that were configured with private or public networking in the Vagrantfile.

Known Issues

• The VirtualBox Guest Additions are not preinstalled, and there are currently no concrete plans of adding them. They are only needed for VirtualBox shared folders (host-only networking and forwarded ports work properly without the Guest Additions). We recommend using NFS instead of VirtualBox shared folders if possible, since the latter are significantly slower and files can be corrupted or not properly updated when sendfile is enabled. If you still want to install the Guest Additions, you can try either vbguest or, if you already use Ansible, take a look at https://github.com/lpancescu/cloud-instance-starter-kit for an example of automatic installation.
• The default sync directory is configured to use rsync. This might cause vagrant up to fail on Windows, where rsync is not installed by default. As a workaround, Windows users can either install rsync via Cygwin or MSYS, or disable the sync directory by adding the line config.vm.synced_folder ".", "/vagrant", disabled: true to the Vagrantfile.
• Vagrant 1.8.5 sets the permissions on ~vagrant/.ssh/authorized_keys to 0644 (world-readable) when replacing the insecure public key with a newly generated one. Since sshd will only accept keys readable just by their owner, vagrant up returns an error, since it cannot connect with the new key and it already removed the insecure key. This is Vagrant bug #7610, which affects all Linux distributions (not just CentOS); you can either downgrade to Vagrant 1.8.4 or wait for 1.8.6 to be released.

Downloads

Only x86_64 images are currently available, for Vagrant’s libvirt and VirtualBox providers.

First-time users can download the official images from Hashicorp’s Atlas. You can use vagrant box add centos/6 for CentOS Linux 6, or vagrant box add centos/7 for CentOS Linux 7.

Existing users can upgrade their boxes directly by Vagrant, e.g. vagrant box update --box centos/7, but the changes will only apply to newly created instances.

Feedback

If you encounter any unexpected issues with the Vagrant images, feel free to ask on the centos-devel mailing list, or in #centos-devel on Freenode.

Acknowledgements

We would like to thank Nico Kadel-Garcia for his valuable insight on preventing sshd from performing reverse DNS lookups.

Official Vagrant images for CentOS Linux 6 and CentOS Linux 7 for x86_64 are now available for download, featuring updated packages to 1st June 2016 and some improvements:

• The size of the boot partition was increased to 250 MB for CentOS Linux 6 and 500 MB for CentOS Linux 7, as the Red Hat documentation recommends (this should prevent the system becoming impossible to update due to lack of space in /boot)
• systemd will create a new machine id on first boot, making it possible to address multiple instances, all created from the official Vagrant image, in the same network (only for CentOS 7)
• on CentOS Linux 6, tuned is preinstalled and it will use the virt-guest profile to improve performance (this was already the case on CentOS 7)
• yum’s infra variable is set to vag, to offer CentOS developers some insight into how many installations are Vagrant instances

Known issues

• The Vagrant sync folder is /home/vagrant/sync instead of /vagrant (which is the Vagrant default). The plan is to create link between the two locations in the next release, and only leave /vagrant in place in the release after the next.
• Instances should always use NTP, but the official images don’t enable any NTP daemon (yet)
• The VirtualBox Guest Additions are not preinstalled, and there are currently no plans of adding them. They are only needed for shared folders; host-only networking and forwarded ports work, although Vagrant displays a warning to the contrary. If you need the VirtualBox Guest Additions and would like to install them automatically, take a look at https://github.com/lpancescu/cloud-instance-starter-kit (pull requests are welcome).

Downloads

Only x86_64 images are currently available, for Vagrant’s libvirt and VirtualBox providers.

First-time users can download the official images from Hashicorp’s Atlas. You can use vagrant box add centos/6 for CentOS Linux 6, or vagrant box add centos/7 for CentOS Linux 7.

Existing users can upgrade their boxes directly by Vagrant, e.g. vagrant box update --box centos/7, but the changes will only apply to newly created instances.

Feedback

If you have any questions or problems with the Vagrant images, feel free to ask on the centos-devel mailing list, or in #centos-devel on Freenode.