From 31705a502d672b0cd917e78b2ff5573b96dd3161 Mon Sep 17 00:00:00 2001 From: Erwan SEITE Date: Wed, 20 Dec 2017 15:40:35 +0100 Subject: [PATCH] change vagrant version --- Vagrantfile | 8 +------- docs/vagrant.md | 2 +- 2 files changed, 2 insertions(+), 8 deletions(-) diff --git a/Vagrantfile b/Vagrantfile index 64a3009c0..536bbff2b 100644 --- a/Vagrantfile +++ b/Vagrantfile @@ -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") @@ -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" diff --git a/docs/vagrant.md b/docs/vagrant.md index 042e8137b..de47159fa 100644 --- a/docs/vagrant.md +++ b/docs/vagrant.md @@ -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`.