vagrantfile

Vagrant: can't get NFS working

怎甘沉沦 提交于 2019-12-04 04:22:56
I'm trying to change my VagrantFile so that it uses an NFS mount instead of the default VirtualBox shared folders. I get this error message: vm: * Shared folders that have NFS enabled do not support owner/group attributes. Host path: . This is my VagrantFile: VAGRANTFILE_API_VERSION = "2" Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| config.vm.box = "ktbartholomew/lamp" config.vm.network "private_network", type: "dhcp" config.vm.synced_folder ".", "/vagrant", type: "nfs" end I can't see any owner or group getting set. Please help! Thanks Vagrant only raises this error when the owner

Vagrant synced folder permissions

ぃ、小莉子 提交于 2019-12-04 02:26:26
I have set up a synced folder in Vagrant, from my Windows host to the guest. Initially the permissions on the files were too open so I added the following mount options: config.vm.synced_folder "../my-folder", "/home/vagrant/my-folder", mount_options: ["dmode=775,fmode=664"] However, I need to add execute permissions on a single file within this folder. chmod +x file has no effect. Is there a way to allow a single item in a shared folder to be executable/have different permissions to the rest of the items in the folder? In the end, I came up with two solutions: 1) Accept all the files being

Allow two or more vagrant VMs to communicate on their own network

心已入冬 提交于 2019-12-03 12:23:54
问题 I want to create multiple servers that can communicate directly with each other without using public IPs. They'll still need internet access but nothing from outside the network will need to connect to them. Creating one box usually works, but when I add additional servers the networking fails. MacOS: 10.8.5 Virtualbox: 4.3.12 GuestOS: Ubuntu "precise64" Using version 2 of the Vagrant config Most of the time if I use private network I get: saltminion01: Warning: Connection timeout. Retrying..

Update a Vagrant Box?

走远了吗. 提交于 2019-12-03 07:26:11
问题 I have updated a box vagrant box update and now when I run vagrant up it boots into the old box. How can I update my box to use the newer version? 回答1: From the Vagrant docs: Finally, you can update boxes with vagrant box update . This will download and install the new box. This will not magically update running Vagrant environments. If a Vagrant environment is already running, you'll have to destroy and re create it to acquire the new updates in the box. The update command just downloads

How to enable internet access inside Vagrant?

瘦欲@ 提交于 2019-12-03 06:20:48
问题 If I run curl google.com , I can't see the output, only a blank page. My Vagrantfile contains: Vagrant.configure("2") do |config| config.vm.box = "trumobi" #config.vm.box_url = "http://192.168.136.129/package.box" config.ssh.default.username = "trumobi" config.vm.network :public_network config.vm.network :forwarded_port, host: 8000, guest: 8000 end 回答1: If you are using Vagrant + VirtualBox + Ubuntu , you might want to add the following block to your VagrantFile: config.vm.provider

Vagrant Config Error - “A box must be specified.”

帅比萌擦擦* 提交于 2019-12-03 06:13:19
The boxes were working fine. Then I halted one (the only one running at the time) and now I can't get either of them back up. Running vagrant up [name] gives me the following error, regardless of which I pick or whether I leave it at vagrant up for them both to come up: There are errors in the configuration of this machine. Please fix the following errors and try again: vm: * A box must be specified. Running latest version of Vagrant (1.7.4). Here is my Vagrantfile in its entirety, comments included (just in case): # Search for boxes here: https://atlas.hashicorp.com/boxes/search # Refer to

vagrant won't start virtual machine - (Errno::EADDRNOTAVAIL)

限于喜欢 提交于 2019-12-03 06:00:33
I really hit a wall with this problem. I am on windows machine (with admin privileges) and I want to start setup my working environment with vagrant. Problem is that I am getting error (down bellow) and I can't find any solution... I am using latest virtual box and vagrant version. Error code: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in `initialize': The requested address is not valid in its context. - connect(2) for "0.0.0.0" port 7755 (Errno::EADDRNOTAVAIL) from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port

Why is Vagrant trying to SSH to Windows guest?

两盒软妹~` 提交于 2019-12-03 05:26:44
My host is running Windows 7 Pro (64 bit). The Guest OS in this case is Windows Server 2008 R2. The 'vagrant up' command is running into an issue where I keep getting: ****default: SSH address: 127.0.0.1:2222 default: SSH username: vagrant default: SSH auth method: password default: Warning: Connection timeout. Retrying... default: Warning: Remote connection disconnect. Retrying... default: Warning: Remote connection disconnect. Retrying... default: Warning: Remote connection disconnect. Retrying... default: Warning: Remote connection disconnect. Retrying...**** till it eventually times out

Vagrant up - VBoxManage.exe error: VT-x is not available (VERR_VMX_NO_VMX) code E_FAIL (0x80004005) gui headless

假装没事ソ 提交于 2019-12-03 04:46:04
问题 Machine: Window10 (64bit). I downloaded the latest VirtualBox, Vagrant and initialized CentOS 6.7 64bit image/url. The following worked successfully in Git-Bash session. 1. vagrant box add "centos67x64" "https://github.com/CommanderK5/packer-centos-template/releases/download/0.6.7/vagrant-centos-6.7.box" 2. vagrant init 3. Updated Vagrantfile (and turned vb.gui option i.e. uncommented that config section in the file). config.vm.provider "virtualbox" do |vb| # Display the VirtualBox GUI when

How to access Vagrant Box in public network

◇◆丶佛笑我妖孽 提交于 2019-12-03 02:40:55
问题 I had created on e box inside vagrant. In the Vagrantfile, I had given the network as Create a private network, which allows host-only access to the machine # using a specific IP. # config.vm.network :private_network, ip: "192.168.33.10" # Create a public network, which generally matched to bridged network. # Bridged networks make the machine appear as another physical device on # your network. config.vm.network :public_network I cant able to access the VagrantBox outside the VLAN. I need to