Official Vagrant images for CentOS Linux 6 and CentOS Linux 7 for x86_64 are now available for download, featuring updated packages to 1st July 2016 and some improvements:
- the default timezone is set to UTC (instead of New York, USA)
- NTP is enabled by default (using ntpd on CentOS Linux 6 and chrony on CentOS Linux 7)
- yum-utils is installed by default on CentOS Linux 7, providing
- The Vagrant sync folder is
/vagrant(which is the Vagrant default). This will be changed in the next release.
- The root password is set to a random string, instead of "vagrant". Use
vagrantuser to gain administrative privileges, no password is required.
- 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 use Ansible, take a look at https://github.com/lpancescu/cloud-instance-starter-kit for an example of automatic installation. The vagrant-vbguest plugin might also work (not tested).
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.
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.
16 thoughts on "Updated CentOS Vagrant Images Available"
Hey, How are you guys able to login. I installed vm by vagrant up and then I am not able to login. I am using 'vagrant' as username and using no password.
Is there any other way around please let me know
I ran into the same problem--the permissions on .ssh/authorized_keys is incorrect. Use "vagrant ssh" to get into the box, the password is "vagrant". Then run "chmod 600 .ssh/authorized_keys".
Running `vagrant ssh` will put you into the machine as the Vagrant user. You can then sudo for root-level access, with no authentication required.
Please chmod ~vagrant/authorized_keys to 600 - this causes the ssh connection to attempt fallback to password authentication
This isn't an issue with the image, but a bug in vagrant. https://github.com/mitchellh/vagrant/issues/7610
You can apply one of the workarounds mentioned in that post or wait for 1.8.6.
I have had the same problem. This is an issue of vagrant. download older version, or wait for next release
Need password for "sudo mysql_secure_installation". Blank is not accepted.
Same problem here, vagrant, root, toor or blank not working
ok In my case the problem was the mysql root password I was able to reset it using this guide:
There is a password, and it turned out to be my first guess: "vagrant".
Not putting GuestEdition for VirtualBox goes against community standard on how to build virtualboxes, and goes against default behavior. Also, will this require Ansible on the host? This might make it not work on Windows if that is the case, as Ansible doesn't support Windows as a host.
Ansible is not required on the host. As the announcement mentions, you can try the vagrant-vbguest plugin, if you need the VirtualBox Guest Additions and the "starter kit" isn't an option for you.
We suck at vagrant ssh password authentication too, is there any fix?
Is there any way to know image(1606.1)disk sizes could up to? 1000G? 500g?
its a sparse file, i believe its setup to goto 60gb by default