Added workaround for vagrant 1.9 and centos vm box (#1738)
This commit is contained in:
parent
d6d58bc938
commit
da61b8e7c9
2 changed files with 8 additions and 2 deletions
8
Vagrantfile
vendored
8
Vagrantfile
vendored
|
@ -3,7 +3,7 @@
|
||||||
|
|
||||||
require 'fileutils'
|
require 'fileutils'
|
||||||
|
|
||||||
Vagrant.require_version ">= 1.8.0"
|
Vagrant.require_version ">= 1.9.0"
|
||||||
|
|
||||||
CONFIG = File.join(File.dirname(__FILE__), "vagrant/config.rb")
|
CONFIG = File.join(File.dirname(__FILE__), "vagrant/config.rb")
|
||||||
|
|
||||||
|
@ -123,6 +123,12 @@ Vagrant.configure("2") do |config|
|
||||||
|
|
||||||
config.vm.network :private_network, ip: ip
|
config.vm.network :private_network, ip: ip
|
||||||
|
|
||||||
|
# workaround for Vagrant 1.9.1 and centos vm
|
||||||
|
# https://github.com/hashicorp/vagrant/issues/8096
|
||||||
|
if Vagrant::VERSION == "1.9.1" && $os == "centos"
|
||||||
|
config.vm.provision "shell", inline: "service network restart", run: "always"
|
||||||
|
end
|
||||||
|
|
||||||
# Only execute once the Ansible provisioner,
|
# Only execute once the Ansible provisioner,
|
||||||
# when all the machines are up and ready.
|
# when all the machines are up and ready.
|
||||||
if i == $num_instances
|
if i == $num_instances
|
||||||
|
|
|
@ -1,7 +1,7 @@
|
||||||
Vagrant Install
|
Vagrant Install
|
||||||
=================
|
=================
|
||||||
|
|
||||||
Assuming you have Vagrant (1.8+) installed with virtualbox (it may work
|
Assuming you have Vagrant (1.9+) installed with virtualbox (it may work
|
||||||
with vmware, but is untested) you should be able to launch a 3 node
|
with vmware, but is untested) you should be able to launch a 3 node
|
||||||
Kubernetes cluster by simply running `$ vagrant up`.<br />
|
Kubernetes cluster by simply running `$ vagrant up`.<br />
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue