Re: [vagrant-up] vmware ubuntu 16.10 rgloader

hello you can email supp...@hashicorp.com what you can try is. copy the ~/.vagrant.d to a folder outside home set VAGRANT_HOME variable to this new home. now, the error seems to came from the box, but looks all is working fine, but failing on vmtools can you try a different box?

Re: [vagrant-up] Virtual COM Port

Hello. If you can came up with the commands you need to run with VBoxManage, from there should be trivial put them inside the Vagrantfile. Alvaro. On Tue, Dec 13, 2016 at 11:51 AM, wrote: > Hello, > > I'm looking for a way to forward virtual serial port to the VM. As

Re: [vagrant-up] Re: "private_network" not configuring running network on Centos 7

Hello. This is a important issue, and Vagrant developers are working on it. You can monitor this isse: https://github.com/mitchellh/vagrant/issues/8096 Thanks Alvaro. On Tue, Dec 13, 2016 at 5:37 AM, Mark H. wrote: > > > On Monday, December 12, 2016 at 9:12:13 AM

Re: [vagrant-up] Ensure admin privileges running vagrant on a Windows host

Hello. Something like this perhaps? http://stackoverflow.com/questions/560366/detect-if-running-with-administrator-privileges-under-windows-xp Couple of ideas to test. (old, but the idea is the important) On Tue, Dec 13, 2016 at 3:11 PM, wrote: > I want to prevent

Re: [vagrant-up] Re: Cannot uninstall/upgrade vagrant

Hello. Please download again the binary. If you are a in a company network, perhaps they have inspection of packages? In the download page is a link to the package and the signatures so you can review the packages are valid. Alvaro. On Wed, Dec 14, 2016 at 5:12 AM,

Re: [vagrant-up] "private_network" not configuring running network on Centos 7

try Vagrant.configure("2") do |config| config.vm.box = "geerlingguy/centos7" config.vm.network "private_network", ip: "192.168.60.4" #workaround config.vm.provision "shell", inline: "ifup enp0s8", run: "always" end -- This mailing list is governed under the HashiCorp Community

Re: [vagrant-up] "private_network" not configuring running network on Centos 7

no need for that. just add in the meantime config.vm.provision "shell", inline: "ifup eth1", run: "always" On Sat, Dec 10, 2016 at 10:27 PM, Matthew Pounsett <m...@conundrum.com> wrote: > > > On Saturday, 10 December 2016 15:11:46 UTC-5, Alva

Re: [vagrant-up] failing to start a docker image

ssh, so vagrant wont be able to login. Alvaro. On Sun, Dec 11, 2016 at 2:50 AM, Asif Iqbal <vad...@gmail.com> wrote: > > > On Sat, Dec 10, 2016 at 2:54 PM, Alvaro Miranda Aguilera < > kiki...@gmail.com> wrote: > >> >> On Fri, Dec 9, 2016 at 5:23

Re: [vagrant-up] "private_network" not configuring running network on Centos 7

Hello I did start one with centos/7 and I can see this: INFO ssh: Execute: # Down the interface before munging the config file. This might # fail if the interface is not actually set up yet so ignore # errors. /sbin/ifdown 'eth1' # Move new config into place mv -f

Re: [vagrant-up] Centos + config.vm.network "private_network", type: "dhcp" => Error: Job for network.service failed because the control process exited with error code

hello. Are you using virtualbox? What network is being created for this? you can check on settings of the VM, network, and select the 2nd interface. Then on Settings of Virtualbox, network, can you check if the network being used have dhcp enabled? Thanks Alvaro. On Thu, Dec 8, 2016 at 11:19

Re: [vagrant-up] Vagrant Port Collisions

hello, This is on VMWare or Virtualbox? In VMWare are issues on 8.5.1 and 8.1.0 and 8.1.1 8.5.2, 8.5.0, 8.0.2 are fine. If not on VMWare, can you share gist when it works and fail? VAGRANT_LOG=debug vagrant up Thanks! Alvaro. On Thu, Dec 8, 2016 at 10:42 PM, Andrew MacNamara

Re: [vagrant-up] "private_network" not configuring running network on Centos 7

On Fri, Dec 9, 2016 at 1:23 AM, Matthew Pounsett wrote: > Vagrant.configure("2") do |config| > config.vm.define "host01" do |host| > host.vm.box = "centos7" > host.vm.box_url = "file://~/src/vagrant/centos7.json" > host.vm.network

Re: [vagrant-up] Error while running vagrant

Hello, Please install the new version of Vagrant, and reboot the machine after install. Alvaro. On Fri, Dec 9, 2016 at 5:11 AM, wrote: > Please help. I got this error when trying to run vagrant.. TQ > > > >

Re: [vagrant-up] Cannot uninstall/upgrade vagrant

What os? How you did install Vagrant? did you install vagrant? how? Alvaro. On Fri, Dec 9, 2016 at 5:16 AM, wrote: > Hi all, > > I can't uninstall or upgrade the vagrant. Why is it? It just say contact > your admin. > > TQ > > -- > This mailing list is governed under

Re: [vagrant-up] failing to start a docker image

On Fri, Dec 9, 2016 at 5:23 AM, Asif Iqbal wrote: > The container started either never left the "stopped" state or > very quickly reverted to the "stopped" state. This is usually > because the container didn't execute a command that kept it running, > and usually indicates a

Re: [vagrant-up] Vagrant SSH permission issue

Hello, I see 2 options. A. create a new user set the public known key there package the box if you are on virtualbox vagrant package package packages a running vagrant environment into a box Then you should be able to overwrite the user with config.ssh.username in the

Re: [vagrant-up] Re: My vagrant boxes are no longer accessible.

vt-x is needed for 64 bit guest. if your box or other you use were 32bit, then they should run fine. On Mon, Dec 5, 2016 at 9:47 PM, Joris Mulliez wrote: > Yeehaa ! > > I've enabled VT-x support in my bios, and it seems to be ok for now... > but I'm not convinced that

Re: [vagrant-up] Re: My vagrant boxes are no longer accessible.

can you test a different box ? hashicorp/precise64 if still fail, can you test vagrant 1.8.6 ? On Sun, Dec 4, 2016 at 3:42 PM, Joris Mulliez wrote: > I forgot to provide system informations : > > I'm running vagrant 1.9, virtualbox 5.1.10 under linux mint 17.1 > >

Re: [vagrant-up] link to localhost using docker as provider

each docker container have a separate networking so localhost inside one container is separate to the network in the other container is like having 2 physical machines, and you want to access a remote service. could you explain a bit why you require localhost for a remote service ? On Fri, Dec

Re: [vagrant-up] Vagrant 1.9.0

\o/ > On 29/11/2016, at 2:16 PM, crobe...@hashicorp.com wrote: > > Hi everyone, > > I'm pleased to announce the release of Vagrant 1.9.0. This release includes > many improvements within Vagrant's internal plugin system. These improvements > include: new commands for repairing or removing

Re: [vagrant-up] fusion plugin not working with uninitialized constant Vagrant (NameError)

hi can you send an email to support @ hashicorp.com ? On Mon, Nov 28, 2016 at 11:47 PM, Simon Green wrote: > Hi, > > I've just bought the Fusion plugin and it's not working for me. > > Running: > > vagrant init geerlingguy/ubuntu1404; vagrant up --provider vmware_fusion > >

Re: [vagrant-up] vagrant to raw disk

hello. Can you explain more? please note that I am asking more information to understand the use case, so please spare few minutes. Vagrant is a tool for development. and development focus on speed (as in velocity to develop faster) so you usually take the simple that works. Is this for PROD

Re: [vagrant-up] Vagrant Language Settings

can you share a log of the vagrant and screenshot of what you see ?? vagrant halt vagrant version for cmd.exe set set VAGRANT_LOG=debug for bash do env export VAGRANT_LOG=debug then vagrant up share the logs and the Vagrantfile you are using try to use gist (gist.github.com) for the output

Re: [vagrant-up] Vagrantfile and variable scope

Hello What happens if you put the shell provider inside the trigger block? config.vm.provision "trigger" do |t| # this code is for clarification sake print "#{aws_access_key}\n" # prints foo print "#{aws_access_secret}\n" # prints bar #

Re: [vagrant-up] Forwarding ports from one machine to another

sets > up port forwarding for guest VM to host. I'm looking to establish > forwarding from one guest VM to another guest VM. > > On Wed, Nov 16, 2016 at 2:53 PM, Alvaro Miranda Aguilera < > kiki...@gmail.com> wrote: > >> on vagrant documentation you need mul

Re: [vagrant-up] (CoreOS/hostonlyif) - vagrant randomly assigns a second interface IP

On Fri, Nov 18, 2016 at 12:17 AM, Jay Christopherson wrote: > kHost.vm.network :private_network, ip: "#{BASE_IP_ADDR}.#{i+99}" vagrant uses eth0 to setup the vm and eth1 is coming from this prpbably: kHost.vm.network :private_network, ip: "#{BASE_IP_ADDR}.#{i+99}" so

Re: [vagrant-up] (CoreOS/hostonlyif) - vagrant randomly assigns a second interface IP

whats your Vagrantfile ? On Thu, Nov 17, 2016 at 11:55 PM, Jay Christopherson wrote: > I'm trying to get a CoreOS cluster up and running to test out Nomad. But > for some reason, Vagrant keeps assigning a second interface IP to the > host-only interface, in the network

Re: [vagrant-up] How to reuse Vagrant parameter with Chef

maybe: username = "ubuntu" config.vm.provider :aws do |aws, override| override.ssh.username = "#{username}" ... end ... config.vm.provision :chef_solo do |chef| chef.json = { username: "#{username}" } ... end ? -- Alvaro -- This mailing list is governed under the

Re: [vagrant-up] vagrant up --provider docker

grant up --provider docker > > but vagrant still try to download boot2docker. > > > > On Tuesday, November 15, 2016 at 1:58:15 PM UTC+1, Alvaro Miranda Aguilera > wrote: >> >> Hello. >> >> If your environment setup DOCKER_HOST >> >> per 1

Re: [vagrant-up] Forwarding ports from one machine to another

on vagrant documentation you need multi machine and port forward https://www.vagrantup.com/docs/multi-machine/ https://www.vagrantup.com/docs/networking/forwarded_ports.html ie Vagrant.configure("2") do |config| config.vm.provision "shell", inline: "echo Hello" config.vm.define "web" do

Re: [vagrant-up] Vagrant Share with HTTPS?

st: 443 >> config.vm.hostname = "ZZ.org" >> config.vm.synced_folder ".", "/var/www", :mount_options => [ >> "dmode=777", "fmode=666"] >> >> # Optional NFS. Make sure to remove other synced_folder line too

Re: [vagrant-up] Re: Static IP for each VM

please share a gist of your vagrantfile On Tue, Nov 15, 2016 at 2:14 PM, wrote: > Thank you very much Alvero, I tried the command you suggested. It worked > for first VM for second one it gave the error below: > ==> web1: Setting hostname... > The following SSH

Re: [vagrant-up] vagrant up --provider docker

Hello. If your environment setup DOCKER_HOST per 1.8.7 you should be able to disable the VM creation. commit: https://github.com/mitchellh/vagrant/commit/8c11b537ba0b691b747f8f5089229033432d257f#diff-bef7cf4806af50c166ed8b2273ffa74fR55 On Tue, Nov 15, 2016 at 1:18 PM, Vincenzo D'Amore

Re: [vagrant-up] Vagant startup

32 bit. I know this because the > VagrantFile specifies trusty32. > > > > I am not sure how to “check C++ redistributable package? > > > > R Kevin Burton > > > > *From: *Alvaro Miranda Aguilera <kiki...@gmail.com> > *Sent: *Monday, November 14, 2016 12:46 AM >

Re: [vagrant-up] Vagant startup

Hello. Can you check C++ redistributable package 32 bit (even if OS is 64bit) is installed? If you still have issues. please do: vagrant destroy set VAGRANT_LOG=debug vagrant up 2>&1 and share a gist of the log message Thanks Alvaro On Thu, Nov 10, 2016 at 8:24 PM,

Re: [vagrant-up] Re: vagrant up: 'ubuntu/trusty32' could not be found

OSX? Try please 1.8.6 On Sun, Nov 13, 2016 at 7:32 PM, Thulasi Krishnan wrote: > I tried uninstalling vagrant and reinstalled it and tried > bento/ubuntu16.04 to get the same error > > [23:56:05][rajatpillai:vagrant]>$ vagrant init bento/ubuntu-16.04; > vagrant up

Re: [vagrant-up] Problem with downloading base boxes 'base' after fresh 'vagrant init'

Hello There is an issue in osx with vagrant 1.8.7 better use 1.8.6 until 1.8.8 is out On Sat, Nov 12, 2016 at 11:27 PM, Joshua Burke wrote: > Hello Again, > > Just wanted to post that the download issue has been resolved. It seems > that the service for

Re: [vagrant-up] Latest Release Appears Broken

Hello. Please test with 1.8.6 On Sat, Nov 12, 2016 at 8:02 PM, DataJock wrote: > I am brand new to Vagrant and tried to go through the Getting Started > pages but had complete failure on the very first item! > > I am using a Mac with MacOS 10.12.1 (*the latest*) > With

Re: [vagrant-up] Static IP for each VM

On Sat, Nov 12, 2016 at 12:35 PM, Jim Jim wrote: > config.vm.define "lb1" do |lb1| > lb1.vm.box="centos/7" > config.vm.network "public_network", ip: "192.168.1.21" > config.vm.provision "shell", inline: <<-SHELL > hostnamectl set-hostname

Re: [vagrant-up] Should I use a box or build a common Vagrantfile?

packer.io can help to build base boxes. My own personal cycle goes like this. start with a basic Vagrant file. add a provision script. (ensure its idempotent, so you can run it twice with no negative issues) Split in to 2 the script one for pre-requirement and other for run time. Once the

Re: [vagrant-up] Git does not work with Vagrant and VMWare

Hello. VMWare filesystem does a good job for general stuff. I haven't heard of issues like this before. Can you check without Vagrant? ie. spin on a VM, setup a shared folder try the same repo. If the issue persists, perhaps opening a ticket with VMWare could help. Alvaro. On Tue, Nov 8, 2016

Re: [vagrant-up] VirtualBox for Macbook Pro (Host) i7

Hello. AMD in the mac book pro I think is related to Video Card. Cpu will be still Intel. Intel / AMD being x86_64 will work without problems. Not sure of the sites you mention, but is always upto .. if you will have a cpu intensive VM, be sure to give resources (multi core, ram), other than

Re: [vagrant-up] Vagrant 1.8.7 Can't Download Boxes

On Sun, Nov 6, 2016 at 9:09 PM, John Jelinek wrote: > INFO subprocess: Starting process: ["/opt/vagrant/embedded/bin/curl", > "-I", "-q", "--fail", "--location", "--max-redirs", "10", "--user-agent", > "Vagrant/1.8.7 (+https://www.vagrantup.com; ruby2.2.5)",

Re: [vagrant-up] Re: Vagrant Up fails with "Stderr: VBoxManage.exe: error: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only"

On Mon, Nov 7, 2016 at 8:49 AM, Krishana Pal Chouhan < kpsingh.chou...@gmail.com> wrote: > Stderr: VBoxManage.exe: error: VT-x is disabled in the BIOS for all CPU > modes (VERR_VMX_MSR_ALL_VMX_DISABLED) > Hello. This happened to be too in Dell XPS 15. Stderr: VBoxManage.exe: error: VT-x is

Re: [vagrant-up] Vagrant Up fails with "Stderr: VBoxManage.exe: error: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only"

Hello Is always good test a default box mkdir precise64 cd precise64 vagrant init -m hashicorp/precise64 vagrant up if this works, then could be an issue on the Vagrantifle you are using. Can you test and share your Vagrantfile ? It seems be an error on networks. If you can comment out the

Re: [vagrant-up] Re: vagrant up fails stating that the vm is not found

able) > VBoxManage.exe: error: Context: "LockMachine(a->session, LockType_Write)" > at line 493 of file VBoxManageModifyVM.cpp > > On Thursday, November 3, 2016 at 1:55:09 PM UTC-5, Alvaro Miranda Aguilera > wrote: >> >> Hello. >> >> Seems to be c

Re: [vagrant-up] Weird behaviour in private_key_path

On Thu, Nov 3, 2016 at 1:20 PM, Steve Button wrote: > config.ssh.private_key_path can you share a gist of the debug log ? vagrant halt VAGRANT_LOG=debug vagrant up Alvaro -- Alvaro -- This mailing list is governed under the HashiCorp Community Guidelines -

Re: [vagrant-up] Re: vagrant up fails stating that the vm is not found

8.6 ) as stated above, and the > C++ x86 (32 bit) is already installed as well (see screenshot below). > where do I set the VAGRANT_LOG variable? Is there a config file that I > edit in a text editor? > [image: Inline image 1] > > On Wed, Nov 2, 2016 at 3:23 PM, Alvaro Miranda Agui

Re: [vagrant-up] Vagrant.configure

hello. mkdir precise64 cd precise64 vagrant init -m hashicorp/precise64 vagrant up does that work? if not, what errors are shown ? On Tue, Nov 1, 2016 at 8:52 PM, harry littrell wrote: > Vagrant.configure("2") do |config| config.vm.box= "boxcutter/centos72" > > I am

Re: [vagrant-up] Re: vagrant up fails stating that the vm is not found

hello what version of Vagrant do you have there? can you try the latest one? For error, can you install C++ redistributable package, 32 bits? (even if OS is 64 bits, 32 bit is required) if still fails: set VAGRANT_LOG=debug vagrant up and share a gist of the generated log. Thanks! Alvaro.

Re: [vagrant-up] Error

On Mon, Oct 31, 2016 at 10:15 PM, Horton X25 wrote: > NS_ERROR_FAILURE (0x80004005) is your host linux ? if yes, it seems you are not having: a. Kernel modules for Virtualbox b. your user may not have permissions to use Virtualbox. if you are in linux, did you

Re: [vagrant-up] Vagrant not working in windows cmd prompt

Do you get anything back? vagrant version? If yes set VAGRANT_LOG=debug vagrant up If not, try with full path c:\HashiCorp\Vagrant\bin\vagrant <- please check, I am doing it by memory. Thanks Alvaro. On Sun, Oct 30, 2016 at 4:44 PM, Petronel Laviniu Malutan < malutanpetro...@gmail.com>

Re: [vagrant-up] newbie help with guest additions

Hello. A bit of back story here. Usually a VM will include guest additions and vagrant by default will try to mount the current folder as /vagrant inside the guest. Usually this works and everyone happy. >From that out of the box experience, some people think virtualbox additions is not the

Re: [vagrant-up] Using machine name with Vagrant commands from any directory

if you have them in separate folders, then global-status + id is the way. if you want to have them with names then you could do multi-machine in the same Vagrantfile: https://www.vagrantup.com/docs/multi-machine/ On Thu, Oct 27, 2016 at 12:42 PM, kenny83ify wrote: >

Re: [vagrant-up] Using machine name with Vagrant commands from any directory

Hello. Can you share the output of vagrant global-status you should be able to use vagrant status vagrant up vagrant stop On Thu, Oct 27, 2016 at 11:29 AM, kenny83ify wrote: > Hi guys, > > As a web developer working on many multi-developer projects, I find >

Re: [vagrant-up] Vagrant 1.8.6, Windows 10, trying to use ssh instead of winrm

storing original > environment... > > Could this be causing problems? > > lucidbee > > > On Wednesday, October 26, 2016 at 12:47:13 PM UTC-7, Alvaro Miranda > Aguilera wrote: >> >> Hi >> >> This is how you can enable winrm for win10 >> >>

Re: [vagrant-up] Vagrant 1.8.6, Windows 10, trying to use ssh instead of winrm

Hi This is how you can enable winrm for win10 https://github.com/MattHodge/PackerTemplates/blob/master/floppy/winrm.ps1 If you want you build boxes, check packer.io, its also a hashicorp tool to build boxes. Have a look at this repo. you should be able to check the scripts.

Re: [vagrant-up] germinateapps/ubuntu16.04-64 -> Can't connect

havent tried the one in your subject. Can you test this one? https://atlas.hashicorp.com/cbednarski/boxes/ubuntu-1604 On Tue, Oct 25, 2016 at 10:54 PM, Stephan Hradek wrote: > Hi! > > vagrant up for this box boots it up - with a 5 minute delay, but I cannot >

Re: [vagrant-up] ISSUE : Authentication failure. Retrying... after Key inserted!

Oct 24, 2016 at 9:48 AM, Stephan Hradek <stephan.hra...@gmail.com> wrote: > > > Am Freitag, 26. August 2016 09:14:03 UTC+2 schrieb Alvaro Miranda Aguilera: >> >> Hello, >> >> This workaround is needed due a bug in Vagrant 1.8.5, the permanent fix >>

Re: [vagrant-up] (vagrant up --provision) + (/etc/nginx/sites-available) + (information lost)

Hello. I will be surprised its vagrant doint anything with nginx. It wont install a package and wont change files. So I will suggest check in the project you are using from where those changes are comming from. > On 23/10/2016, at 3:52 AM, Hercules Andrade wrote: >

Re: [vagrant-up] Windows guest synced folders and IIS permission problem

hello I haven't done it, so I am thinking loud, but maybe have the IIS service to run under vagrant user? in that way wil have access to the files copied or even mount point from Vagrant. Alvaro. On Thu, Oct 20, 2016 at 3:40 PM, Thomas Messier wrote: > So I've spent

Re: [vagrant-up] Doesn't start the operating system on VM

, it work. > > On Thursday, October 20, 2016 at 2:27:39 PM UTC+3, Alvaro Miranda Aguilera > wrote: >> >> hello. >> >> Vagrant works with templates. >> >> Do the base template work? >> >> mkdir precise32 >> cd precise32 >> vagrant init -m

Re: [vagrant-up] IE 11 problem - keep getting 'problem with this website’s security certificate' (although works fine on Google Chrome which uses the same certificate store)

Hello Perhaps you can check here: https://github.com/scotch-io/scotch-box/issues Alvaro On Thu, Oct 20, 2016 at 2:06 PM, Gavin wrote: > I am running Vagrant 1.8.6 (the latest version at the time of the post) > and running this on my Windows 10 Home machine. I have setup

Re: [vagrant-up] Doesn't start the operating system on VM

hello. Vagrant works with templates. Do the base template work? mkdir precise32 cd precise32 vagrant init -m hashicorp/precise32 vagrant up Does this work? Then mkdir precise64 cd precise64 vagrant init -m hashicorp/precise64 vagrant up Does this one works? On Thu, Oct 20, 2016 at 11:46

Re: [vagrant-up] where is default vagrantfile to define NAT interface ssh port 2222 to guest 22

nt ssh from the > vagrant host itself but I want to remote ssh into the guest from other > servers in the same network as the host. Assuming the host ip is > 100.100.100.1, I can have a remote server do ssh -p > vagrant@100.100.100.1 to get into the guest. > > Hongjun >

Re: [vagrant-up] where is default vagrantfile to define NAT interface ssh port 2222 to guest 22

hello that is internally done in Vagrant by design. So the information is on vagrant source code https://github.com/mitchellh/vagrant/blob/7eb1091a7102dd4d2ebab762ee1658689a889880/plugins/kernel_v2/config/vm.rb#L436-L444 anything in particular you are after ? On Tue, Oct 18, 2016 at 8:22 PM,

Re: [vagrant-up] Slow vagrant up on Windows guest

Hello, What you can do is repackage the VM after some changes. If you edit the services and move most of them from start to deferred/delayed start will help to boot it faster. On Tue, Oct 18, 2016 at 2:33 AM, Thomas Messier wrote: > I'm getting started using

Re: [vagrant-up] Creating Ghost Image From Existing Machine Using Vagrant

you can use tools to create a VM from existing host, and then install winrm + user/pass to make it work so as for the question, the answer is yes and it should work. Alvaro. On Mon, Oct 17, 2016 at 4:03 PM, wrote: > Hi, > > I am trying to create a

Re: [vagrant-up] Vagrant + Packer + AWS + Virtual box: The box you attempted to add doesn't match the provider you specified.

hello by default Vagrant up witll try virtualbox. as you can see here: Provider expected: virtualbox Provider of box: aws try: vagrant up --provider aws and make sure you have the aws plugin vagrant plugin list vagrant plugin install vagrant-aws Thanks Alvaro. On Sat, Oct 15, 2016 at 10:09

Re: [vagrant-up] Windows shutdown issue: "VirtualBox Interface has active connections"

Hello if you get that message again, could you share the output of VBoxManage list vms That will show if there is still a VirtualBox vm running. On Fri, Oct 14, 2016 at 5:58 PM, Carl Gross wrote: > Hi all. Whenever I end my Vagrant session, I do so by running *vagrant

Re: [vagrant-up] Beginner looking for help

Hello Guy I am chilean (spanish) speaker that speaks no dutch and lives near Rotterdam. As for your question. When you install vagrant, its the best let it install on the default path. c:\hashicorp\vagrant then, your user need to have permissions on 3 directories. say your user is guy your

Re: [vagrant-up] Vagrant with aws and docker

Hello Andy Vagrant core can manage Virtualbox and docker. If your host OS is linux, you can just use vagrant + docker and will run fine. For AWS, you can install vagrant-aws plugin, and manage an AWS EC2 without requiring virtualbox on your host. Alvaro. On Fri, Oct 14, 2016 at 9:57 PM, Andy

Re: [vagrant-up] ubuntu-xenial-16.04-cloudimg.vmdk: Truncated tar archive

Hello HashiCorp only provides the boxes under hashicorp/ organization. I can confirm the current box in ubuntu/xenial is not working. In the meantime, can you test this one? https://atlas.hashicorp.com/cbednarski/boxes/ubuntu-1604 If you would like to report this issue, I am afraid I don't

Re: [vagrant-up] How to completely remove VVV files from my computer?

leted? Or do I always have to > manually delete the files myself? > > What does *vagrant status/vagrant global-status* do? > > Thanks, > > Carl > > On Thu, Oct 13, 2016 at 3:54 PM, Alvaro Miranda Aguilera < > kiki...@gmail.com> wrote: > >> hello >> &

Re: [vagrant-up] how to change network subnet 10.0.2.0/24 for network created by vagrant by default ?

t Alvaro > that works fine. > > I've read the doc and the ebook 'Vagrant Up and Running" but I didn't find > this configuration option > > Have a nice day > > Bruno > > > Le mercredi 12 octobre 2016 18:50:16 UTC+2, Alvaro Miranda Aguilera a > écrit : >>

Re: [vagrant-up] how to change network subnet 10.0.2.0/24 for network created by vagrant by default ?

hello Vagrant doesn't create the network, its VirtualBox. Try this: Vagrant.configure(2) do |config| config.vm.box = "hashicorp/precise64" config.vm.provider "virtualbox" do |v| v.customize ["modifyvm", :id, "--natnet1", "10.0.3/24"] end end Alvaro. On Wed, Oct 12, 2016 at

Re: [vagrant-up] How to enable two-way folder sync in Vagrant with VirtualBox?

Thanks Alvaro. On Wed, Oct 12, 2016 at 6:27 AM, Adnan Latif <alatif@gmail.com> wrote: > I am using its default settings. I don't know what are default settings > used sync or rsync. > > > On Wednesday, 12 October 2016, Alvaro Miranda Aguilera <kiki...@gmail.

Re: [vagrant-up] help with unable to ssh after Sierra upgrade

y other Mac running Sierra > doesn't have a ~/.ssh directory at all, so I don't think Apple added it as > a part of Sierra, unless it was a part of not allowing DSA keys). Well, > regardless of how it broke, I'm ecstatic it now works! > > Thank you for all of your help and suggestions

Re: [vagrant-up] Re: 500 Internal Server Error while trying to get a bento box

Hello, Are some issues being investigated in atlas. You can always check here: https://status.hashicorp.com/ Thanks Alvaro. On Wed, Oct 12, 2016 at 5:29 AM, Hakan Baba wrote: > After about 10-15 minutes, I gave another try. > It looks like the problem has been resolved

Re: [vagrant-up] How to enable two-way folder sync in Vagrant with VirtualBox?

Hello There is no difference from where you update the files if the shared folder is on virtualbox/vmware/nfs the only ones i think may be a problem is with rsync since that is meant to be host -> guest So as long you don't use rsync you should be fine.. what are you using today? Alvaro On

Re: [vagrant-up] WinRM::WinRMAuthorizationError, vagrant up fails for windows 10 vm

me global vagrant state? After I changed the password to > vagrant the winrm authorization problem went away. > > lucidbee > > > > On Sunday, October 9, 2016 at 11:45:17 AM UTC-7, Alvaro Miranda Aguilera > wrote: >> >> Hello >> >> Can you try a different box? &

Re: [vagrant-up] WinRM::WinRMAuthorizationError with a Windows 2012 R2 guest

On Tue, Oct 11, 2016 at 8:46 AM, Rui Lopes wrote: > config.winrm.transport = :plaintext > config.winrm.basic_auth_only = true > Hello, If the connection doesn't get drop, the script shouldn't fail. If the connection gets drop, then Vagrant may report back

Re: [vagrant-up] help with unable to ssh after Sierra upgrade

On Tue, Oct 11, 2016 at 8:59 AM, Kirstin Veltman wrote: > /Users/Raven/.ssh/config: line 1: Bad configuration option: useroaming Hello Can you share your .ss/config ? Its very clear telling us there is an error, and what you copy past it seems have a typo ie:

Re: [vagrant-up] Vagrant 1.7 + error

hello official way it to use the vagrant installer. https://www.vagrantup.com/downloads.html Alvaro On Sun, Oct 9, 2016 at 10:13 PM, Vang wrote: > I tried upgrading to from 1.6 to 1.7 and 1.8 and get the following error. > Is it because vagrant 1.7+ requires ruby 2? > >

Re: [vagrant-up] Re: Second vagrant machine doesn't serve php

On Sun, Oct 2, 2016 at 9:54 PM, Kenoli Oleari wrote: > http://http://localhost:8080/Sites3/world.php > > > The browser says "Localhost refuses to connect" > > hello http://http://localhost:8080/Sites3/world.php The browser says "Localhost refuses to connect" Welll the url

Re: [vagrant-up] help with unable to ssh after Sierra upgrade

On Fri, Oct 7, 2016 at 7:53 AM, Kirstin Veltman wrote: > /Users/Raven/.ssh/config: terminating, 1 bad configuration options Hello Can create a new user in the host machine and test? it seems the error is on your user .ssh folder: /Users/Raven/.ssh/config: terminating,

Re: [vagrant-up] Vagrant supporting Ansible -u command

Hello I think the issue is the user being used. if you log in using vagrant, that user wont have permissions in that folder. So if you want to use ansible_user, then you could update the Vagrantfile for config.ssh.username config.ssh.password Thanks Alvaro. On Sat, Oct 8, 2016 at 12:00 PM,

Re: [vagrant-up] Symlinks

nothing to do with vagrant. You will hit the same if you don't use vagrant. if you are using the shared folder, take note that is not a full filesystem, is a psudo-one, so some features work and other doesnt. on VMWare symlink can be created, but there sometimes the issue that fast changes

Re: [vagrant-up] WinRM::WinRMAuthorizationError, vagrant up fails for windows 10 vm

Hello Can you try a different box? I just test this one and works fine witn WinRM: MattHodge/Windows2012R2-WMF5-NOCM The messages you see on the DEBUG, are Vagrant logic, in the first part of the run, Vagrant goes to all the

Re: [vagrant-up] WinRM::WinRMAuthorizationError with a Windows 2012 R2 guest

Hello, Better use a link to a gist, rather than the log. I haven't checked the log, but I would like to ask what changed? If you did update OS and Vagrant/Virtualbox, any chance you can test with what used to work? And any chance to test in a different computer? and finally, with a different

Re: [vagrant-up] Multi-machine Vagrant file to use one VM?

Usually the Vagrantfile lives with the code, so is part of the version control, the provisioning scripts to create the VM can be used later to deploy the app/code into production, etc. If you want to have a big Vagrantifile like that, it will work, there is a way to stop the VMs starting if you

Re: [vagrant-up] Two (accidental) VirtualBox machines from one Vagrant file

Hello, When you do vagrant up, Vagrant read the Vagrantfile. them it create a folder .vagrant and there is information there that tells vagrant what Box is being used. Say we start creating a new Vagrantfile: *0* kikitux@mini ~/Downloads/precise64* (master)* $ vagrant status .. default

Re: [vagrant-up] How can I install a plugin for a vagrant box with a self built vagrant?

Hello If there is only your host, you can try to replace this file: plugins/guests/linux/cap/network_interfaces.rb Alvaro. On Wed, Oct 5, 2016 at 1:52 PM, wrote: > Hello all, > > I'm trying to run the DC/OS Vagrant Box, which depends on > vagrant-hostmanager plugin.

Re: [vagrant-up] Error in executing VBoxManage

gt; > Interface: > > IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0} > > Also, no this happens to both boxes. > On Thursday, September 29, 2016 at 10:41:37 AM UTC-6, Alvaro Miranda > Aguilera wrote: >> >> hello >> >> try to use virtualbox gui to stop and

Re: [vagrant-up] Vagrant Share not working with HTTPS

if you are > comfortable with sending this request in plain text. If you are unable to > do so, you should contact the creator of the sharing session and let them > know you are not able to access the VM over SSL/TLS." > > > What am I doing wrong? > On Thursday, September

Re: [vagrant-up] Second vagrant machine doesn't serve php

Hello Is very hard to guess what you are doing (commands) and what the goal is. If you could setup a github repo and share some lines on: "this is what I want to do" "this is what I have tried" "here is where It fail, I want this but i get this" or something similar. happy to help, but just

Re: [vagrant-up] Error: Failed to find Vagrant !

Hello Vagrant 1.8.6 has been released, please upgrade. After the installation finish, you are ask to reboot, please do. After that it should work. If doesnt' check c:\hashicorp\vagrant is there and there is vagrant.exe somewhere Thanks alvaro. On Sat, Oct 1, 2016 at 6:51 AM, Neel Shah

Re: [vagrant-up] Vagrant installation on Windows7

Hello Were you able to remove the plugin? On Fri, Sep 30, 2016 at 1:50 PM, Tattwa wrote: > > Thanks Alvaro, > > > I saw two licences while installing Vagrant on Window7 in the > ''Term' screen.' > First License : The MIT License (free) > Second License : Vagrant

Re: [vagrant-up] Vagrant installation on Windows7

Hello vagrant plugin list vagrant plugin uninstall Should allow you remove the plugin. but from there any user can install that or other plugin. If you go to the route to make some directory read only (ie [HOME]/.vagrant.d/gems/gems) the user can just use set VAGRANT_HOME=[new_folder] so is

Re: [vagrant-up] change winrm logon credentials mid-vagrantfile

hello, you could use a trick like create a file after the provision, and wrap creds around if block ? On Thu, Sep 29, 2016 at 6:50 PM, Brian Gonzalez wrote: > Is there a way to change the winrm creds after a "config.vm.provision > :reload" is executed? this would

<    5   6   7   8   9   10   11   12   13   14   >