vagrant-provision

问题 I'm using Laravel Homestead (Vagrant, Ubuntu). My host computer is Windows 10 running VirtualBox. As admin (since I've already seen tons of answers that say lack of permissions is usually why people have problems with symlinks), I open Git Bash and run this: vagrant@vboxHomestead:~/Code/myproject$ ls -lah /home/vagrant/foo/blah total 0 drwxrwxrwx 1 vagrant vagrant 0 Mar 17 23:09 . drwxrwxrwx 1 vagrant vagrant 0 Mar 17 22:36 .. -rwxrwxrwx 1 vagrant vagrant 0 Mar 17 23:09 asdf.txt vagrant

问题 I'm using Laravel Homestead (Vagrant, Ubuntu). My host computer is Windows 10 running VirtualBox. As admin (since I've already seen tons of answers that say lack of permissions is usually why people have problems with symlinks), I open Git Bash and run this: vagrant@vboxHomestead:~/Code/myproject$ ls -lah /home/vagrant/foo/blah total 0 drwxrwxrwx 1 vagrant vagrant 0 Mar 17 23:09 . drwxrwxrwx 1 vagrant vagrant 0 Mar 17 22:36 .. -rwxrwxrwx 1 vagrant vagrant 0 Mar 17 23:09 asdf.txt vagrant

问题 So I have a vagrant / puppet setup for my project* and am running Ubuntu 14.04 on it. It just broke, without changing anything. puppet module install puppetlabs-apt inside the VM fails with the following lines: Error: Could not execute operation for 'puppetlabs/apt' The server being queried was https://forge.puppetlabs.com The HTTP response we received was '302 Found' Check the author and module names are correct. I'm using this module for quite some time and it seems like it just stopped

问题 I have several Vagrantfile , each one for a different provider , since Vagrant has a limitation that doesn't allow to make two or more provisions at the same time using the same Vagrantfile . So, I split into two or more Vagrantfiles , but my "body", my provisions scripts are the same for both, the only thing that changes is the provider block. For example: local_nagios/Vagrantfile # -*- mode: ruby -*- # vi: set ft=ruby : require 'yaml' set = YAML.load_file '../../../settings.yaml' Vagrant

问题 Hi all I am trying to pull a repo from my github to a vagrant box via ansible, refering this github issue. I have registered an ssh from my host with the github. And below is the part in the playbook where I'm trying to pull; - name: install git apt: name=git - name: create the ssh public key file copy: src=/home/user/.ssh/id_rsa.pub dest=/root/.ssh/id_rsa.pub mode=0644 - name: create the ssh private key file copy: src=/home/user/.ssh/id_rsa dest=/root/.ssh/id_rsa mode=0600 - name: setup git

问题 Is it possible to reverse the order of provisioners from innermost to outermost when using a multi-machine setup? I want a small shell provisioner to create some facts in /etc/facter/facts.d/ before provisioning with puppet, to mimic our current setup as much as possible. (I have inherited a large puppet repo and am trying to create a Vagrant testbed for it before I start doing changes.) The puppet settings are the same for every box, but requires the shell provisioner to run first. Here's an

问题 I'm trying to install and run Elasticsearch in Vagrant. The issue is that when I try to run elasticsearch I get the following error: log4j:ERROR setFile(null,true) call failed. java.io.FileNotFoundException: /home/vagrant/elasticsearch-2.3.0/logs/elasticsearch.log (No such file or directory) at java.io.FileOutputStream.open0(Native Method) at java.io.FileOutputStream.open(FileOutputStream.java:270) at java.io.FileOutputStream.<init>(FileOutputStream.java:213) at java.io.FileOutputStream.<init

问题 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

问题 I'm following this link https://github.com/acfreitas/oraclebox I tried to include the code for setting up VM storage size on my Vagrant. But i'm getting error like below. ==> vagrant: Running provisioner: shell... vagrant: Running: C:/Users/skywork/AppData/Local/Temp/vagrant-shell20151111-11660-1l3hhe.sh ==> vagrant: ++ '[' grep -ic 64GB /sizeDisk ']' ==> vagrant: /tmp/vagrant-shell: line 4: [: too many arguments ==> vagrant: ++ sudo fdisk -u /dev/sdb ==> vagrant: Welcome to fdisk (util-linux

问题 In summary, When provisioning my vagrant box using Ansible, I get thrown a mysterious error when trying to clone my bitbucket private repo using ssh. The error states that the "Host key verification failed". Yet if I vagrant ssh and then run the ' git clone ' command, the private repo is successfully cloned. This indicates that the ssh forward agent is indeed working and the vagrant box can access my private key associated with the bitbucket repo. I have been struggling for two days on this