Skip to content

Commit

Permalink
change vagrant version
Browse files Browse the repository at this point in the history
  • Loading branch information
wanix committed Mar 26, 2018
1 parent 5f5d0ff commit 31705a5
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 8 deletions.
8 changes: 1 addition & 7 deletions Vagrantfile
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@

require 'fileutils'

Vagrant.require_version ">= 1.9.0"
Vagrant.require_version ">= 2.0.0"

CONFIG = File.join(File.dirname(__FILE__), "vagrant/config.rb")

Expand Down Expand Up @@ -135,12 +135,6 @@ Vagrant.configure("2") do |config|

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

# Disable swap for each vm
config.vm.provision "shell", inline: "swapoff -a"

Expand Down
2 changes: 1 addition & 1 deletion docs/vagrant.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
Vagrant Install
=================

Assuming you have Vagrant (1.9+) installed with virtualbox (it may work
Assuming you have Vagrant (2.0+) installed with virtualbox (it may work
with vmware, but is untested) you should be able to launch a 3 node
Kubernetes cluster by simply running `$ vagrant up`.<br />

Expand Down

0 comments on commit 31705a5

Please sign in to comment.