date:20180124

Re: [vagrant-up] Password prompt on bringing up Vagrant although it is specified in Vagrantfile

2018-01-24 Thread Shashank Korada

Hi Alvaro,

Thanks for your reply.
I think the ssh_settings that you are referring to is for accessing the VM. 
I was referring to accessing the remote server.
As per plugin provider options this is what I found and tried to use

https://github.com/vagrant-libvirt/vagrant-libvirt#provider-options

Any idea if I am maybe still using it incorrectly ?


On Thursday, January 25, 2018 at 8:21:55 AM UTC+5:30, Alvaro Miranda 
Aguilera wrote:
>
> hello
>
> seems you got the user/pass on the wrong block.
>
> https://www.vagrantup.com/docs/vagrantfile/ssh_settings.html
>
> config.ssh.username
>
> or 
> x.ssh.username
>
>
>
>
> On Wed, Jan 24, 2018 at 7:23 AM, Shashank Korada  > wrote:
>
>> Hello,
>>
>> I am trying to launch VMs on a remote server by specifying the 
>> username/password for the server in the Vagrantfile but on running "vagrant 
>> up" it still prompts me for the password.
>> How do I avoid being prompted for the password?
>>
>> This is my current Vagrantfile:
>>
>> VAGRANTFILE_API_VERSION = "2"
>> Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
>>   config.ssh.forward_agent = true
>>   config.vm.define "test-remote-vm-libvirt" do |x|
>> x.vm.box = "ceph/ubuntu-xenial"
>> x.vm.hostname = "test-remote-vm-libvirt"
>> x.vm.network :private_network, ip: 10.0.10.100
>> x.vm.provider :libvirt do |v|
>>   v.driver = "kvm"
>>   v.host = "10.73.40.52"
>>   v.username = "skorada"
>>   v.password = "mypassword"
>>   v.connect_via_ssh = true
>>   v.memory = 2
>>   v.cpus = 2
>>   v.nested = true
>> end
>>   end
>> end
>>
>> Console logs on bringing up vagrant:
>>
>> skorada@test-server:~/home/vagrant/$ vagrant up
>> Bringing machine 'test-remote-vm-libvirt' up with 'libvirt' provider...
>>
>> root@localhost's password:   ==> PASSWORD 
>> PROMPT
>>
>> ==> test-remote-vm-libvirt: Creating image (snapshot of base box volume).
>> ==> test-remote-vm-libvirt: Creating domain with the following settings...
>> ==> test-remote-vm-libvirt:  -- Name:  
>> master_test-remote-vm-libvirt
>> ==> test-remote-vm-libvirt:  -- Domain type:   kvm
>> ==> test-remote-vm-libvirt:  -- Cpus:  2
>> ==> test-remote-vm-libvirt:  -- Feature:   acpi
>> ==> test-remote-vm-libvirt:  -- Feature:   apic
>> ==> test-remote-vm-libvirt:  -- Feature:   pae
>> ==> test-remote-vm-libvirt:  -- Memory:6000M
>> ==> test-remote-vm-libvirt:  -- Management MAC:
>> ==> test-remote-vm-libvirt:  -- Loader:
>> ==> test-remote-vm-libvirt:  -- Base box:  ceph/ubuntu-xenial
>> ==> test-remote-vm-libvirt:  -- Storage pool:  default
>> ==> test-remote-vm-libvirt:  -- Image:
>>  /var/lib/libvirt/images/master_test-remote-vm-libvirt.img (301G)
>> ==> test-remote-vm-libvirt:  -- Volume Cache:  default
>> ==> test-remote-vm-libvirt:  -- Kernel:
>> ==> test-remote-vm-libvirt:  -- Initrd:
>> ==> test-remote-vm-libvirt:  -- Graphics Type: vnc
>> ==> test-remote-vm-libvirt:  -- Graphics Port: 5900
>> ==> test-remote-vm-libvirt:  -- Graphics IP:   127.0.0.1
>> ==> test-remote-vm-libvirt:  -- Graphics Password: Not defined
>> ==> test-remote-vm-libvirt:  -- Video Type:cirrus
>> ==> test-remote-vm-libvirt:  -- Video VRAM:9216
>> ==> test-remote-vm-libvirt:  -- Sound Type:
>> ==> test-remote-vm-libvirt:  -- Keymap:en-us
>> ==> test-remote-vm-libvirt:  -- TPM Path:
>> ==> test-remote-vm-libvirt:  -- INPUT: type=mouse, bus=ps2
>> ==> test-remote-vm-libvirt: Creating shared folders metadata...
>> ==> test-remote-vm-libvirt: Starting domain.
>> ==> test-remote-vm-libvirt: Waiting for domain to get an IP address...
>> ==> test-remote-vm-libvirt: Waiting for SSH to become available...
>> Pseudo-terminal will not be allocated because stdin is not a terminal.
>> skorada@localhost's password:> 
>> PASSWORD PROMPT
>> ==> test-remote-vm-libvirt: Setting hostname...
>> ==> test-remote-vm-libvirt: Configuring and enabling network interfaces...
>> ==> test-remote-vm-libvirt: Rsyncing folder: /home/vagrant/ => /vagrant
>>
>> skorada@localhost's password:   > 
>> PASSWORD PROMPT
>>
>>
>> Am I missing any ssh config that is required? Also dont understand why I 
>> am being prompted for a password multiple times
>> Any pointers would be helpful.
>>
>> Regards
>>
>> -- 
>> This mailing list is governed under the HashiCorp Community Guidelines - 
>> https://www.hashicorp.com/community-guidelines.html. Behavior in 
>> violation of those guidelines may result in your removal from this mailing 
>> list.
>>  
>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>> IRC: #vagrant on Freenode
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Vagrant" group.
>> To unsubscribe from this group and stop receiving emails from it,

Re: [vagrant-up] Re: Vagrant up virtual box boot error in windows 8

2018-01-24 Thread venis

Ok thanks. I not getting proper solution. i will check with virtual box 
forums

On Thursday, January 25, 2018 08:18:52 UTC + 5: 30 Alvaro Miranda Aguilera 
wrote:
>
> you need to fix that error
>
> is coming from virtualbox, not vagrant
>
> On Wed, Jan 24, 2018 at 5:34 AM,  
> wrote:
>
>> I did same as you have mentioned. 
>> Previously and now also i am getting the same error.
>> VM never went to power on state. it is always in Off state
>> Please check and suggest me
>>
>>
>> 
>>
>>
>> On Wednesday, January 24, 2018 00:57:00 UTC + 5: 30 Alvaro Miranda 
>> Aguilera wrote:
>>>
>>> hello
>>>
>>> open virtualbox, poweroff the VM, turn it on, see if you can connect
>>>
>>> user vagrant
>>> password vagrant
>>>
>>>
>>>
>>> On Tue, Jan 23, 2018 at 4:07 PM,  wrote:
>>>
 Thanks for your reply.
 I did as you have mentioned but still i am getting same error.
 Please check and help me to fix


 


 On Tuesday, January 23, 2018 17:17:27 UTC + 5:30 wrote ve ... @ 
 cityfashion.asia:
>
>
> 0down votefavorite 
> 
>
>
> 
>
> I have installed vagrant (vagrant_2.0.1_x86_64.msi) and virtual box 
> (VirtualBox-4.3.12-93733-Win.exe, i also tried with 
> VirtualBox-5.2.6-120293-Win.exe) in windows 8 OS in my HP compaq 
> latop I have enabled virtualisation in BIOS But while executing 'vagrant 
> up' i am getting the below error  I googled for answers and none of them 
> worked for me. Please help me to fix this issue. I am trying to to setup 
> 'ubuntu/trusty64' box
>
> I am getting this error:
>
> ==> default: Waiting for machine to boot. This may take a few m The 
> guest machine entered an invalid state while waiting for it to boot. 
> Valid 
> states are 'starting, running'. The machine is i 'poweroff' state. Please 
> verify everything is configured properly and try again.
>
> If the provider you're using has a GUI that comes with it, it is often 
> helpful to open that and watch the machine, since t GUI often has more 
> helpful error messages than Vagrant can retr For example, if you're using 
> VirtualBox, run vagrant up while VirtualBox GUI is open.
>
> The primary issue for this error is that the provider you're us is not 
> properly configured. This is very rarely a Vagrant issue
>
>
> -- 
 This mailing list is governed under the HashiCorp Community Guidelines 
 - https://www.hashicorp.com/community-guidelines.html. Behavior in 
 violation of those guidelines may result in your removal from this mailing 
 list.
  
 GitHub Issues: https://github.com/mitchellh/vagrant/issues
 IRC: #vagrant on Freenode
 --- 
 You received this message because you are subscribed to the Google 
 Groups "Vagrant" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to vagrant-up+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/vagrant-up/59d77798-176b-49d5-a12c-2eab337d2f21%40googlegroups.com
  
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>>
>>> -- 
>>> Alvaro
>>>
>>> -- 
>> This mailing list is governed under the HashiCorp Community Guidelines - 
>> https://www.hashicorp.com/community-guidelines.html. Behavior in 
>> violation of those guidelines may result in your removal from this mailing 
>> list.
>>  
>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>> IRC: #vagrant on Freenode
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Vagrant" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to vagrant-up+...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/vagrant-up/2b91cb0c-4836-4ebb-9ffe-60566b68850f%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Alvaro
>
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines -

Re: [vagrant-up] How to add 2nd Hostonly private NIC in Vagrant box?

2018-01-24 Thread Alvaro Miranda Aguilera

hello

network is reset on each vagrant up.

the package box need to have the first interface confgured with dhcp

use the vagrant networking to add either private or public

you can add multiples interfaces this way

first nic / nat should be there since its what vagrant uses to configure
the guest

alvaro

On Wed, Jan 24, 2018 at 1:19 AM, Robert Wang 
wrote:

> Most of time we build Vagrant box without specific NIC, by default Vagrant
> add NAT NIC when launch vm using box,but sometime want to do pre-config on
> private network inside box.
>
> Tried it but when import box,found there is only NAT NIC there, seems
> private NIC removed when build box.
>
> Any idea is this for purpose or any solution I didn't know yet?
>
> Many thanks.
>
> BR/
> Robert
>
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/8582fe86-44e3-4edf-929a-091bbcabd688%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Alvaro

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0ewBWYoDDeNcB3ajsk6Vma77ST79zdCmi9TN1x%3Dr9YOPAA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Password prompt on bringing up Vagrant although it is specified in Vagrantfile

2018-01-24 Thread Alvaro Miranda Aguilera

hello

seems you got the user/pass on the wrong block.

https://www.vagrantup.com/docs/vagrantfile/ssh_settings.html

config.ssh.username

or
x.ssh.username




On Wed, Jan 24, 2018 at 7:23 AM, Shashank Korada 
wrote:

> Hello,
>
> I am trying to launch VMs on a remote server by specifying the
> username/password for the server in the Vagrantfile but on running "vagrant
> up" it still prompts me for the password.
> How do I avoid being prompted for the password?
>
> This is my current Vagrantfile:
>
> VAGRANTFILE_API_VERSION = "2"
> Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
>   config.ssh.forward_agent = true
>   config.vm.define "test-remote-vm-libvirt" do |x|
> x.vm.box = "ceph/ubuntu-xenial"
> x.vm.hostname = "test-remote-vm-libvirt"
> x.vm.network :private_network, ip: 10.0.10.100
> x.vm.provider :libvirt do |v|
>   v.driver = "kvm"
>   v.host = "10.73.40.52"
>   v.username = "skorada"
>   v.password = "mypassword"
>   v.connect_via_ssh = true
>   v.memory = 2
>   v.cpus = 2
>   v.nested = true
> end
>   end
> end
>
> Console logs on bringing up vagrant:
>
> skorada@test-server:~/home/vagrant/$ vagrant up
> Bringing machine 'test-remote-vm-libvirt' up with 'libvirt' provider...
>
> root@localhost's password:   ==> PASSWORD
> PROMPT
>
> ==> test-remote-vm-libvirt: Creating image (snapshot of base box volume).
> ==> test-remote-vm-libvirt: Creating domain with the following settings...
> ==> test-remote-vm-libvirt:  -- Name:
> master_test-remote-vm-libvirt
> ==> test-remote-vm-libvirt:  -- Domain type:   kvm
> ==> test-remote-vm-libvirt:  -- Cpus:  2
> ==> test-remote-vm-libvirt:  -- Feature:   acpi
> ==> test-remote-vm-libvirt:  -- Feature:   apic
> ==> test-remote-vm-libvirt:  -- Feature:   pae
> ==> test-remote-vm-libvirt:  -- Memory:6000M
> ==> test-remote-vm-libvirt:  -- Management MAC:
> ==> test-remote-vm-libvirt:  -- Loader:
> ==> test-remote-vm-libvirt:  -- Base box:  ceph/ubuntu-xenial
> ==> test-remote-vm-libvirt:  -- Storage pool:  default
> ==> test-remote-vm-libvirt:  -- Image: /var/lib/libvirt/images/
> master_test-remote-vm-libvirt.img (301G)
> ==> test-remote-vm-libvirt:  -- Volume Cache:  default
> ==> test-remote-vm-libvirt:  -- Kernel:
> ==> test-remote-vm-libvirt:  -- Initrd:
> ==> test-remote-vm-libvirt:  -- Graphics Type: vnc
> ==> test-remote-vm-libvirt:  -- Graphics Port: 5900
> ==> test-remote-vm-libvirt:  -- Graphics IP:   127.0.0.1
> ==> test-remote-vm-libvirt:  -- Graphics Password: Not defined
> ==> test-remote-vm-libvirt:  -- Video Type:cirrus
> ==> test-remote-vm-libvirt:  -- Video VRAM:9216
> ==> test-remote-vm-libvirt:  -- Sound Type:
> ==> test-remote-vm-libvirt:  -- Keymap:en-us
> ==> test-remote-vm-libvirt:  -- TPM Path:
> ==> test-remote-vm-libvirt:  -- INPUT: type=mouse, bus=ps2
> ==> test-remote-vm-libvirt: Creating shared folders metadata...
> ==> test-remote-vm-libvirt: Starting domain.
> ==> test-remote-vm-libvirt: Waiting for domain to get an IP address...
> ==> test-remote-vm-libvirt: Waiting for SSH to become available...
> Pseudo-terminal will not be allocated because stdin is not a terminal.
> skorada@localhost's password:>
> PASSWORD PROMPT
> ==> test-remote-vm-libvirt: Setting hostname...
> ==> test-remote-vm-libvirt: Configuring and enabling network interfaces...
> ==> test-remote-vm-libvirt: Rsyncing folder: /home/vagrant/ => /vagrant
>
> skorada@localhost's password:   >
> PASSWORD PROMPT
>
>
> Am I missing any ssh config that is required? Also dont understand why I
> am being prompted for a password multiple times
> Any pointers would be helpful.
>
> Regards
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/453f75a4-41b0-4a6e-ae22-79b8f86b5717%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Alvaro

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those

Re: [vagrant-up] Re: Vagrant up virtual box boot error in windows 8

2018-01-24 Thread Alvaro Miranda Aguilera

you need to fix that error

is coming from virtualbox, not vagrant

On Wed, Jan 24, 2018 at 5:34 AM,  wrote:

> I did same as you have mentioned.
> Previously and now also i am getting the same error.
> VM never went to power on state. it is always in Off state
> Please check and suggest me
>
>
> 
>
>
> On Wednesday, January 24, 2018 00:57:00 UTC + 5: 30 Alvaro Miranda
> Aguilera wrote:
>>
>> hello
>>
>> open virtualbox, poweroff the VM, turn it on, see if you can connect
>>
>> user vagrant
>> password vagrant
>>
>>
>>
>> On Tue, Jan 23, 2018 at 4:07 PM,  wrote:
>>
>>> Thanks for your reply.
>>> I did as you have mentioned but still i am getting same error.
>>> Please check and help me to fix
>>>
>>>
>>> 
>>>
>>>
>>> On Tuesday, January 23, 2018 17:17:27 UTC + 5:30 wrote ve ... @
>>> cityfashion.asia:


 0down votefavorite
 


 

 I have installed vagrant (vagrant_2.0.1_x86_64.msi) and virtual box
 (VirtualBox-4.3.12-93733-Win.exe, i also tried with
 VirtualBox-5.2.6-120293-Win.exe) in windows 8 OS in my HP compaq latop
 I have enabled virtualisation in BIOS But while executing 'vagrant up' i am
 getting the below error  I googled for answers and none of them worked for
 me. Please help me to fix this issue. I am trying to to setup
 'ubuntu/trusty64' box

 I am getting this error:

 ==> default: Waiting for machine to boot. This may take a few m The
 guest machine entered an invalid state while waiting for it to boot. Valid
 states are 'starting, running'. The machine is i 'poweroff' state. Please
 verify everything is configured properly and try again.

 If the provider you're using has a GUI that comes with it, it is often
 helpful to open that and watch the machine, since t GUI often has more
 helpful error messages than Vagrant can retr For example, if you're using
 VirtualBox, run vagrant up while VirtualBox GUI is open.

 The primary issue for this error is that the provider you're us is not
 properly configured. This is very rarely a Vagrant issue


 --
>>> This mailing list is governed under the HashiCorp Community Guidelines -
>>> https://www.hashicorp.com/community-guidelines.html. Behavior in
>>> violation of those guidelines may result in your removal from this mailing
>>> list.
>>>
>>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>>> IRC: #vagrant on Freenode
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Vagrant" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to vagrant-up+...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/vagrant-up/59d77798-176b-49d5-a12c-2eab337d2f21%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Alvaro
>>
>> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/2b91cb0c-4836-4ebb-9ffe-60566b68850f%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Alvaro

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop

[vagrant-up] [ANN] Removal of legacy Vagrant Cloud (Atlas) URLs next Friday (February 2nd)

2018-01-24 Thread Justin Campbell

If you're using Vagrant >= 1.9.6, you can safely ignore this notice. 
Otherwise, please read on for affected versions and a workaround.

For a period of time, Vagrant was released with a default Vagrant Cloud URL 
of https://atlas.hashicorp.com. Support for downloading Vagrant boxes from 
this domain will be removed on Friday, February 2nd, 2018. The correct URL 
is https://vagrantcloud.com.

Affected Vagrant versions and release dates:

>= 1.7.0 (12/9/2014),
< v1.9.6 (6/28/2017)

We recommend that you upgrade to the latest version of Vagrant (2.0.1) at 
https://www.vagrantup.com/downloads.html

If you'd like to continue using the versions mentioned above, you'll need 
to set the VAGRANT_SERVER_URL environment variable in order for box 
downloads/updates to continue working:

# macOS and Linux
export VAGRANT_SERVER_URL="https://vagrantcloud.com;

# Windows (CMD)
set VAGRANT_SERVER_URL="https://vagrantcloud.com;

# Windows (Powershell)
$env:VAGRANT_SERVER_URL="https://vagrantcloud.com;

If you have any questions or concerns, you can reply here, or email 
support+vagrantcl...@hashicorp.com.

Thanks! -Justin

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/0f530309-691f-4a14-bc18-378eb504f138%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Password prompt on bringing up Vagrant although it is specified in Vagrantfile

Re: [vagrant-up] Re: Vagrant up virtual box boot error in windows 8

Re: [vagrant-up] How to add 2nd Hostonly private NIC in Vagrant box?

Re: [vagrant-up] Password prompt on bringing up Vagrant although it is specified in Vagrantfile

Re: [vagrant-up] Re: Vagrant up virtual box boot error in windows 8

[vagrant-up] [ANN] Removal of legacy Vagrant Cloud (Atlas) URLs next Friday (February 2nd)

6 matches

Site Navigation

Mail list logo

Footer information