vagrant

Cannot install global homestead: Your requirements could not be resolved

瘦欲@ 提交于 2020-01-11 08:44:35
问题 I am trying to install homestead on OSX 10.11. I want to be up and running building laravel applications. I cannot run homestead from the command line. When I try to install it globally I get an error: $ composer global require "laravel/homestead=~2.0" Changed current directory to /Users/connorleech/.composer ./composer.json has been updated Loading composer repositories with package information Updating dependencies (including require-dev) Your requirements could not be resolved to an

failed to find free socket port for process dispatcher when trying remote debug

白昼怎懂夜的黑 提交于 2020-01-11 07:14:08
问题 Highlights: windows 10 host machine ubuntu vagrant box (virtualbox) as guest vm using vagrant port forwarding as like this: config.vm.network "forwarded_port", guest: 1234, host: 12340 IDE: IntelliJ IDEA with Ruby plugin The Issue: I've tried to set up remote ruby debug following this guide and getting an error in IDE: " failed to find free socket port for process dispatcher ". It looks this issue is not IntelliJ-specific, I was able to reproduce it with latest RubyMine as well. From IDEA's

MongoDB on Vagrant via Port Forwarding issue

≯℡__Kan透↙ 提交于 2020-01-11 03:57:05
问题 I've recently installed mongodb on my CentOS 6 VM running on Vagrant. I added port forwarding to Vagrantfile to forward the mongo port config.vm.forward_port 27017, 127017 I configured mongod to start automatically when the server starts and have confirmed that the service starts as intended. however when i run mongo localhost:127017 from my host machine (not vagrant) i get the following error MongoDB shell version: 1.8.2 connecting to: localhost:127017/test Fri Jan 20 13:58:28 getaddrinfo(

translate vagrant statements in docker statements

。_饼干妹妹 提交于 2020-01-07 08:37:25
问题 I have to translate a vagrant file in docker commands for setting up a test server. I have no experiance in using docker and for the following command I found no solution. Vagrant.configure("2") do |config| config.vm.network(:forwarded_port, guest: 5432, host: 5432, host_ip: "127.0.0.1") I tried something like docker network create --gateway 127.0.0.1 forwarded_port But I found no way to set the ports and I'm not sure if "forwarded_port" is the name for my network or an argument for a method

Error: [Errno 71] Protocol error: pyvenv

谁说我不能喝 提交于 2020-01-07 08:33:08
问题 I am using Centos7 with vagrant and virtualbox on windows10. I am trying to create pyvenv virtual environment to develop python web apps with django. I have installed python 3.4. However, when I type pyvenv-3.4 name_of_environment , it gives back an error Error: [Errno 71] Protocol error: 'lib' -> '/vagrant/django_apps/app1/name_of_environment/lib64' What is wrong? 回答1: pyvenv-3.4 --without-pip name_of_environment worked looks like pip was not installed. thanks for the help. 来源: https:/

Which one is best: Apache Ambari cluster on Physical system with 5 Machine or install on virtual machine with diffrent 5 VM?

戏子无情 提交于 2020-01-07 04:55:10
问题 Hi I am working on One of my project which I have created VM of 5 Machine and it is working fine in development environment but I have some confusion regarding VM cluster is good or need to go with physical system cluster. 回答1: Hadoop was developed for physical systems but it will function with varying degrees of success in virtual environments, it depends on the specific environment. This is actually quite a common question on the hadoop mailing lists and was specifically addressed by the

Installing puppetlabs/apt fails with '302 Found'

核能气质少年 提交于 2020-01-07 02:21:11
问题 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

Vagrant “Timed out while waiting for the machine to boot.”

生来就可爱ヽ(ⅴ<●) 提交于 2020-01-07 02:15:15
问题 I had a previously working setup with vagrant 1.8.1 and virtualbox 5.0.22, but after upgrading to vagrant 1.8.5 and 5.1.0, i now get the dreaded "Timed out while waiting for the machine to boot." Any options other than downgrading? Full output: Bringing machine 'centos7' up with 'virtualbox' provider... ==> centos7: Importing base box 'centos/7'... ==> centos7: Matching MAC address for NAT networking... ==> centos7: Checking if box 'centos/7' is up to date... ==> centos7: Setting the name of

Vagrant VBoxGuessAdditions error

回眸只為那壹抹淺笑 提交于 2020-01-06 21:22:20
问题 I created a Vagrant box with Ubuntu + KDE. I have a problem with resolution screen in this. A perhaps way to resolve this is install new VBoxGuessAdditions. Indeed I change boolean (from false to true) on this line on my vagrantFile : config.vbguest.auto_update = true With this line at 'false' value I have no problem for up my vagrant. But when a set this config at 'true' I have this error : Installing the Window System drivers Installing X.Org Server 1.17 modules ...done. Setting up the

How use local environment variable with Vagrant?

ぃ、小莉子 提交于 2020-01-06 20:15:33
问题 I'm passing my local environment variables like this: # -*- mode: ruby -*- # vi: set ft=ruby : Vagrant.configure(2) do |de| de.vm.box = 'ubuntu/trusty64' de.vm.hostname = 'virtual_machine' de.vm.network 'public_network', bridge:ENV['NETWORK_INTERFACE'], ip:'192.168.2.170' de.vm.provider "virtualbox" do |v| v.memory = 4096 v.cpus = 2 end de.vm.synced_folder '.', '/vagrant', disabled:true de.vm.synced_folder '../../synced/shared/', '/shared/' de.vm.synced_folder '../../synced/devops/', '/devops