Re: [vagrant-up] stdin is not a tty

hello can you explain better what the issue is, what should be happening, and what is not working. more you can share the better, you can copy paste logs snips to share what you see, you can put a github repo so anyone can vagrant up and have the same environment, etc. stdin is not a tty is a

Re: [vagrant-up] Vagran boxes vs AWS nodes - why Vagrant boxes are so fast?

hello Vagrant boxes are minimal in size so copy template to VM is just seconds. They don't have anything installed so boot until ready is quick. The most you include in the base box the less you need to provision to make it usable. in the AWS, deploy an AMI to a new instance can take some time

Re: [vagrant-up] Re: vagrant up fails: error on vmrun file in use

hello jacob try first a different box to ensure the setup is working properly hashicorp/precise64 if this box works then we can assume is the box you are using. The directory that lucas is suggesting is ~/.vagrant.d/boxes being ~ your home directory inside that path you will see a directory

[vagrant-up] Vagrant file - public network not getting dns

Hi everyone I have a vagrant file that has: config.vm.box = "fso/xenial64-desktop" config.vm.network "forwarded_port", guest: 80, host: 19721, host_ip: "127.0.0.1" config.vm.network "public_network", bridge: "Intel(R) Ethernet Connection I217-LM" There is also config.vm.provision with

Re: [vagrant-up] macOS, Vagrant, VirtualBox, shell provider powershell bug?

Windows 10 Vagrant 2.0.0 Virtualbox 5.1.30 vagrant up worked fine ==> default: Running provisioner: shell... default: Running: shell/NotifyGuiAppsOfEnvironmentChanges.ps1 as c:\tmp\vagrant-shell.ps1 ==> default: 1 ==> default: SUCCESS: Specified value was saved. ==> default: Running

Re: [vagrant-up] Who creates the "generic" Vagrant boxes?

Hello If there is no email/contact information in the page of the org or in each box then I am afraid there no a way to contact them. The same goes for a pseudo changelog, if there is no info on changes. Alvaro. On Fri, Nov 3, 2017 at 1:00 AM, Lucas Rangit Magasweran <

Re: [vagrant-up] 'vagrant up' or 'vagrant ssh' problem

Hello The vagrantfile you did share is missing some commands, so I would suggest fix it and see how to share feedback # -*- mode: ruby -*- # vi: set ft=ruby : # Vagrantfile API/syntax version. Don't touch unless you know what you're doing! VAGRANTFILE_API_VERSION = "2" # Installation script

Re: [vagrant-up] Re: vagrant up fails: error on vmrun file in use

Thanks Alvaro, So using the hashicorp/precise64 box vagrant times out on starting VMware. So I am at a loss except to contact VmWare support but I think they will not help since I am using Vagrant. On Friday, November 3, 2017 at 6:11:37 AM UTC-4, Alvaro Miranda Aguilera wrote: > > hello jacob

[vagrant-up] WSL does not auto detect?

I have installed vagrant version 2.0.1 into wsl using the debian package. It does not seem to be automatically detecting it. This causes it to think it's a standard linux system and it can't find the windows virtualbox executable even though it is on the path. -- This mailing list is governed

Re: [vagrant-up] Cannot ping between Precise(Ubuntu) and VSRX(Juniper) VM's

you need to check if there is a gw set between the networks. Alvaro. On Thu, Nov 2, 2017 at 4:57 PM, Barry Keegan wrote: > I can ping between VSRX 1 and 2 on the virtualbox__intnet: "twenty" > network so I don't believe there are any configuration issues with the >

Re: [vagrant-up] Vagrant file - public network not getting dns

if you need or want to use a different dns you could use a provisioning script to do that. or check this : https://serverfault.com/questions/453185/vagrant-virtualbox-dns-10-0-2-3-not-working On Fri, Nov 3, 2017 at 1:21 PM, rcpunc wrote: > Hi everyone > > I have

[vagrant-up] Re: stdin is not a tty

// None of the Vagrant scripts will run: `vagrant up`, `vagrant halt`, `vagrant suspend`, and `vagrant destroy` // nothing runs they all get stopped with the following output error message $ vagrant destroy ==> default: Running triggers before destroy... ==> default: Executing command "vagrant

Re: [vagrant-up] Vagrant file - public network not getting dns

I tried adding - vb.customize ["modifyvm", :id, "--natdnshostresolver1", "on"] but it had no effect. The vm should get its dns settings from the corporate network, but no idea why it doesn't On Friday, 3 November 2017 12:49:38 UTC, Alvaro Miranda Aguilera wrote: > > if you need or want to use