Blog.CentOS.org
News, views, and reports on CentOSUpdated CentOS Vagrant Images Available (v1803.01)
Tuesday , 10, April 2018 announcement 12 CommentsWe are pleased to announce new official Vagrant images of CentOS Linux 6.9 and CentOS Linux 7.4.1708 for x86_64 (based on the sources of RHEL 7.4). All included packages have been updated to 3rd April 2018.
Known Issues
- 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, to prevent errors on "vagrant up".
- 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
- The vagrant-libvirt plugin is only compatible with Vagrant 1.5 to 1.8
- 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).
- Some people reported "could not resolve host" errors when running the centos/7 image for VirtualBox on Windows hosts. Try adding the following line to your Vagrantfile:
vb.customize ["modifyvm", :id, "--natdnshostresolver1", "off"]
Recommended Setup on the Host
Our automatic testing is running on a CentOS Linux 7 host, using Vagrant 1.9.4 with vagrant-libvirt and VirtualBox 5.1.20 (without the Guest Additions) as providers. We strongly recommend using the libvirt provider when stability is required.
Downloads
The official images can be downloaded from Vagrant Cloud. We provide images for HyperV, libvirt-kvm, VirtualBox and VMware.
If you never used our images before:
vagrant box add centos/6 # for CentOS Linux 6, or... 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:
$ export box_checksum="4440a10744855ec2819d726074958ad6cff56bb5a616f6a45b0a42d602aa1154" $ vagrant box add --checksum-type sha256 --checksum $box_checksum --provider libvirt --box-version 1803.01 centos/7
Feedback
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.
Ackowledgements
We would like to warmly thank Fabian Arrotin and Thomas Oulevey for their work on the build infrastructure, as well as Patrick Lang from Microsoft for testing and feedback on the Hyper-V images.
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;
- Kirill Kalachev, for reporting and debugging the host name errors with VirtualBox on Windows hosts.
Fraser Goffin says: Thanks for providing this box, this is the first time I have used it.
Tried to use the ovf from this box to do some further provisioning with Packer and output a new box, but Packer fails with
Error waiting for SSH: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none], no supported methods remain
I used the following pretty std settings for the builder ...
"communicator": "ssh",
"ssh_username": "{{user `ssh_username`}}",
"ssh_password": "{{user `ssh_password`}}",
"ssh_port": 22,
"ssh_wait_timeout": "10000s",
"ssh_pty": "false",
where ssh_username and ssh_password are both "vagrant".
I note that if I just use the box as/is and spin up a virtual box from it, that
etc/ssh/sshd_config
has ...
PasswordAuthentication no
I didn't see anything in these notes about this, can you enlighten and advise me please.
Kind Regards
Fraser.
Fraser Goffin says: Answering my own question ....
First it was documented in the Centos6 release notes that password authentication *is* disabled because it is insecure.
If you still want to proceed,
you can either add the Vagrant insecure private key and then login will fall-back to 'publickey' and successfully connect (see Packer config below), or you could re-package the box (using vagrant package --output foo.box) after first changing sshd_config to allow password authentication.
Be aware that both of these should be considered as insecure unless you take other steps. As a local dev environment for me behind a NAT network its fine but YMMV :-
"ssh_private_key_file" : "insecure_private_key",
alex says: Please leave the man-pages and doc files in the image for the next release.
Those are not taking up much space , and are very useful when you are on the command line.
@alex
You may want to send the request to the centos-devel list or file at http://bugs.centos.org to get your voice heard. 🙂
Robert Kelly says: Any chance we could get an update that includes 3.10.0-862* kernel? To install the VirtualBox guest additions we need to build with kernel-devel, and the packages for 3.10.0-693* packages seem to be disappearing from the repos, at least for kernel-devel. This means that just installing the vagrant-vbguest plugin does not work, it actually causes the startup of the box to fail. This is easy to replicate right now, just try to create any new CentOS vagrant box and use vagrant-vbguest for shared folders.
kbsingh says: best way to influence the vagrant images is to actually hit up github for the repo and post an issue / patch there.
Robert Kelly says: @kbsingh Which github repo are you referring to?
I have MacOS with
Virtualbox - Version 5.2.12 r122591 (Qt5.6.3)
Vagrant 2.1.1
vagrant-bindfs (1.1.0)
vagrant-hostmanager (1.8.8)
vagrant-share (1.1.9)
vagrant-vbguest (0.15.1)
My config is :
Vagrant.configure(2) do |config|
config.vm.box = "centos/7"
config.vm.network "private_network", ip: "192.168.33.133"
config.vm.provision "shell", inline: "yum -y update"
config.vm.synced_folder "./", "/opt/myproj", id: "vagrant-root", type: "virtualbox"
config.vm.provider "virtualbox" do |vb|
vb.memory = "10000"
end
end
After I execute "vagrant up" i have an error:
/sbin/mount.vboxsf: mounting failed with the error: No such device
Is this related to what Robert Kelly mentions? I mean - outdated kernel?
aharden 
confused says: "The vagrant-libvirt plugin is only compatible with Vagrant 1.5 to 1.8"
"Our automatic testing is running on a CentOS Linux 7 host, using Vagrant 1.9.4 with vagrant-libvirt"
i am confused
-
"Not supported" doesn't mean that it won't work with newer Vagrant versions, just that the upstream authors don't consider the combination stable enough for production purposes (or that they don't want bug reports related to newer versions). There used to be installation failures with some Vagrant 1.9.x versions, but the combination I use for the automated tests on the CentOS CI infrastructure seems to work reliably. I also use vagrant-libvirt on Fedora 27 without any problems.
joe says: I would like to build a vagrant box with a bigger disk size (--disk-size=80), but I am new to koji and get this error when running `do_vagrant_cbs.sh 7`:
`koji: error: no configuration for profile name: cbs`
Where is this profile stored?