vagrant-windows

问题 Testing default example $ vagrant init hashicorp/precise32 $ vagrant up My box: Windows 8.1 VirtualBox 5.0.2 Vagrant 1.7.4 Intel i7-4700MQ CPU witch seems to have Intel® Virtualization Technology (VT-x) http://ark.intel.com/products/75117/Intel-Core-i7-4700MQ-Processor-6M-Cache-up-to-3_40-GHz I know this is common error but after trying everything I still cannot make it work While VM shows: And I can log in successfully: Firewall / Antivirus turned off. Hyper-V is not installed I have tried

问题 What should I add in Vagrant file to prevent asking (after vagrant up command) Which interface should the network bridge to? Available bridged network interfaces: 1) Intel(R) 82579LM Gigabit Network Connection 2) VMware Virtual Ethernet Adapter for VMnet1 3) VMware Virtual Ethernet Adapter for VMnet8 I want to select the #1 option. Current I need to enter "1" manually. Please help! 回答1: in your Vagrantfile, you should add config.vm.network "public_network", bridge: "Intel(R) 82579LM Gigabit

问题 I'm following the old tutorials off of gettingstartedwithdjango.com . This series is quite old and I'm new to Django which is why I hit that site in the first place. It became my first introduction to Vagrant. Because the series is old and there are now new versions of Django, Vagrant, etc, I've found just getting through the first tutorial was quite difficult. This was mainly just the gap between Django v1.4 and the current version 1.9 which is what I'm running, including some syntax

问题 I'm following the old tutorials off of gettingstartedwithdjango.com . This series is quite old and I'm new to Django which is why I hit that site in the first place. It became my first introduction to Vagrant. Because the series is old and there are now new versions of Django, Vagrant, etc, I've found just getting through the first tutorial was quite difficult. This was mainly just the gap between Django v1.4 and the current version 1.9 which is what I'm running, including some syntax

问题 I have some projects in Laravel, and when I have to give some maintenance to them, sometimes when I run vagrant up , it warns me up that I have a newer version of the laravel box, homestead, like the message below: A newer version of the box 'laravel/homestead' is available! You currently have version '1.1.0'. The latest is version '2.0.0'. Run `vagrant box update` to update. My question is, always when I run vagrant box update , it tooks like a decade to download the newer version of the box

问题 Whenever I try to connect to my local Vagrant, I get this error when I run ssh vagrant@127.0.0.1:2222 from the Windows git bash: ssh: connect to host 127.0.0.1:2222 port 22: Bad file number It was working previously, so I'm not sure what could have caused this. When I try to do an SFTP connection in PHPStorm 8, I get this error: Connection to '127.0.0.1' failed. SSH_MSG_DISCONNECT: 2 Too many authentication failures for vagrant I've tried vagrant destroy with vagrant box remove laravel

问题 I'm using windows with homestead and I'm trying to enter vagrant up on the command line but I'm getting this error: C:/www/Homestead/scripts/homestead.rb:106:in read': No such file or directory @ rb_sysopen - C:/Users/Niall/.ssh/id_rsa (Errno::ENOENT) from C:/www/Homestead/scripts/homestead.rb:106:in block (2 levels) in configure' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/plugins/kernel_v2/config/vm_provisioner.rb:72:in call' from C:/HashiCorp/Vagrant/embedded/gems/gems

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

问题 I'm working on vagrant and running host on 127.0.0.1:5000, but problem is cmd is not detecting any host, due which workbench is continuously giving error on making ssh connection. Here is my host running : And flask server is running on port :5000 And workbench is countinously giving error. I think error is due to workbench is unable to locate host : In vagrant file forwarded_port is 5000 : 来源： https://stackoverflow.com/questions/37321679/windows-cmd-not-detecting-flask-server

问题 I am running into an issue with Vagrant/Docker-Compose that seems to be specific to Windows. Here's an overview of the setup and orchestration: Vagrant using a boot2docker box Several docker containers running inside of boot2docker VM Vagrantfile that runs several shell scripts Inside of those shell scripts, I run commands that call out from the boot2docker VM to it's child Docker containers. An example of those commands look like: docker exec -i $(docker-compose ps -q $DOCKER_DBSVC) /bin