vagrantfile

How to automatically install Ansible Galaxy roles, using Vagrant?

给你一囗甜甜゛ 提交于 2019-12-12 08:34:27
问题 Using one playbook only, then it's not possible to have Ansible automagically install the dependent roles. At least according to this SO thread. But, I have the added "advantage" of using Vagrant and Vagrant's Ansible local provisioner . Any tricks I may apply? 回答1: Update 2018-11-22! Given the evolution of software, I can not guarantee that all of the "old stuff/answer" below is still legit and won't set your machine on fire lol. I do, however, maintain a Vagrantfile on GitHub that does

Why is Vagrant trying to SSH to Windows guest?

强颜欢笑 提交于 2019-12-12 07:34:46
问题 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.

Shared Vagrant configuration across multiple projects

主宰稳场 提交于 2019-12-12 04:11:05
问题 I have a few services, each one living in its own Git repository. Each service is self-contained and runs independently from each other. I want them to run in the same VM. How do you use Vagrant to set up a shared development environment containing these services? (Please note that I want to avoid creating a Vagrantfile per repo.) 回答1: Create a custom cookbook/puppet manifest or shell provisioner that will checkout individual git repository and run the service. More details/configuration

vagrant provision: read line from keyboard/stdin

狂风中的少年 提交于 2019-12-12 03:28:10
问题 And so, I have a Vagrantfile with code: VAGRANTFILE_API_VERSION = "2" Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| ... config.vm.provision "shell", inline: 'echo "Read line:" && read t && echo "$t"' ... end and when I execute vagrant provision i have that output: $ vagrant provision ... ==> default: Running provisioner: shell... default: Running: inline script ==> default: Read line: ==> default: exit that is no suggest enter a line from keyboard/stdin! What I should do for reading

There was an error while executing `VBoxManage`, a CLI used by Vagrant

♀尐吖头ヾ 提交于 2019-12-12 02:26:59
问题 When I run the command "vagrant up", I am getting the following error, Can any one tell me what was the issue and how to resolve it ? E:\World_Bank\Vagrant_05Aug2014>vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'test-phil'... ==> default: Matching MAC address for NAT networking... ==> default: Setting the name of the VM: Vagrant_05Aug2014_default_1407255316443_73721 ==> default: Destroying VM and associated drives... There was an error

vagrant up command issue

懵懂的女人 提交于 2019-12-12 00:06:22
问题 I am new with Vagrant. My supervisor want me to run a website. First of all he told me to install VirtualBox and Vagrant. He sent me bootstrap.sh and Vagrantfile files. He told me to copy this in a folder called "data_repo". After that he told me to run "vagrant up" command from "data_repo". I did that but it is giving me following error: A Vagrant environment or target machine is required to run this command. Run `vagrant init` to create a new Vagrant environment. Or, get an ID of a target

Vagrant provision with Docker

倖福魔咒の 提交于 2019-12-11 21:52:46
问题 I want to run a docker image on Vagrant machine. My Vagrantfile is straingforward: VAGRANTFILE_API_VERSION = "2" Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| config.vm.box = "ubuntu/trusty64" config.vm.synced_folder "./project/", "/project/" config.vm.network "forwarded_port", guest: 8000, host: 8000 config.vm.network :public_network, bridge: 'eth0' config.vm.provision "docker" do |d| d.run 'ldap', image: '10.5.6.19:5000/ldap' end end I have this image on my machine: >sudo docker

Vagrant creating an incorrect client.pem on chef node (I think)

两盒软妹~` 提交于 2019-12-11 20:56:48
问题 I'm using Vagrant to create a chef node, and it spins up the image and then the initial chef-client run fails. When I ssh into the machine, delete /etc/chef/client.pem , and run sudo chef-client again, it succeeds, but without the run_list that I passed in from vagrant. This is what the failure looks like: $ vagrant up Bringing machine 'default' up with 'vsphere' provider... ==> default: Calling vSphere CloneVM with the following settings: ==> default: -- Template VM: myOrg/vm/myFolder

Node Can't connect to vagrant box

左心房为你撑大大i 提交于 2019-12-11 18:27:05
问题 I am not sure if this is the correct place to ask my question, but really I am out of ideas, and my clock is ticking. In short, I got a new machine that I need to make development ready. This project is based on rather old program versions, that is a task to update. In short I have set up the Vagrant (1.8.1) in VirtualBox (5.0.14). Chef (0.10.0) created all dependencies successfully and I can SSH to machine and see all is fine, all services are running as set in VagrantFile. Vagrant box is

Vagrant and NGINX only works on ports other than 80

北慕城南 提交于 2019-12-11 11:24:14
问题 For the purpose of this post, I am using Vagrant to launch NGINX (through Docker, but that is not important I don't think). My Vagrant looks like the following: VAGRANTFILE_API_VERSION = "2" Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| #Assign Box and VM Properties config.vm.box = "ubuntu/trusty64" config.vm.provider "virtualbox" do |v| v.memory = 1024 v.cpus = 2 end # Network config.vm.network "forwarded_port", guest:80, host: 80 #--> DOESN'T WORK localhost config.vm.network