Re: [vagrant-up] Destroying a cluster

[Alvaro Miranda Aguilera]

vagrant status

and use those names

or vagrant global-status and use the id


Alvaro.


On Tue, Feb 13, 2018 at 1:14 PM, Mahmood Naderan 
wrote:

> Hi,
> I have installed a dcos via vagrant on a local laptop for tests. I want to
> delete the machines and install from scratch. The virtualbox manager shows
> m1.dcos
> a1.dcos
> p1.dcos
> boot.dcos
>
> The following destroy command fails
>
> D:\dcos-vagrant> vagrant destroy m1.dcos
>  INFO dcos-vagrant: Validating Plugins...
>  INFO dcos-vagrant: Validating User Config...
>  INFO dcos-vagrant: Validating Installer Checksum...
>  INFO dcos-vagrant: Using DC/OS Installer: installers/dcos/dcos_generate_
> config-1.10.2.sh
>  INFO dcos-vagrant: Using DC/OS Config: etc/config-1.10.yaml
>  INFO dcos-vagrant: Validating Machine Config...
>  INFO dcos-vagrant: Validating Command...
>  INFO dcos-vagrant: Configuring VirtualBox Host-Only Network...
> The machine with the name 'm1.dcos' was not found configured for
> this Vagrant environment.
>
> May I know what should I do?
>
> --
> 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/2a7b0cfb-68f8-4159-85fb-75f43d3884d5%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/CAHqq0eyk%2BkSKyB0%2BTqqZNkD6iMNRHUWZ%2BBoHCDgUianBNRopug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Old ubuntu/xenial64 box version points to current

[Alvaro Miranda Aguilera]

Hello

Thats how canonical manage their boxes in vagrant cloud

What I did once was create my own boxes pointing to those, however there is
no guarantee the old boxes will stay for ever.
Other option is just create your own boxes.

https://github.com/cbednarski/packer-ubuntu

Alvaro.

On Wed, Feb 14, 2018 at 5:34 AM, Pavel Martynov  wrote:

> Hi everyone!
>
> I found that I can not download old version of
> ubuntu/xenial64 20171028.0.0. If I do "vagrant.exe box add ubuntu/xenial
> --box-version 20171028.0.0", then vagrant downloads box to
> ~/.vagrant.d/boxes/ubuntu-VAGRANTSLASH-xenial64/20171028.0.0/virtualbox/,
> but in box.ovf will be line " ovf:id="ubuntu-xenial-16.04-cloudimg-20171028">".
> Look at versions mismatch.
>
> Additionally, I test download with curl:
>
> $ curl -X HEAD -i https://vagrantcloud.com/ubuntu/boxes/xenial64/
> versions/20171028.0.0/providers/virtualbox.box
> HTTP/1.1 302 Found
> 
> Location: https://app.vagrantup.com/ubuntu/boxes/xenial64/
> versions/20171028.0.0/providers/virtualbox.box
> 
>
> $ curl -X HEAD -i https://app.vagrantup.com/ubuntu/boxes/xenial64/
> versions/20171028.0.0/providers/virtualbox.box
> 
> Location: http://cloud-images.ubuntu.com/xenial/current/xenial-
> server-cloudimg-amd64-vagrant.box
> 
>
> So, https://vagrantcloud.com/ubuntu/boxes/xenial64/versions/20171028.0.0/
> providers/virtualbox.box actually points to "current", which is 20171028
> now.
> This is a bug or expected behavior?
>
> --
> 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/3d81a39f-edc6-4476-b394-4d38f66d76b8%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/CAHqq0exL59CiQ034diGCRUZczowXH8eW%3DJHi%2BRbAjgOb8LCP_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Requested NFS version or transport protocol not supported

[Monte Gardner]

I have a vagrant set up that was built by someone else at my company. Other 
co-workers say it works for them on their (similarly configured) apple 
laptops. When I run vagrant up, I get the following:

=> default: Configuring and enabling network interfaces...
default: SSH address: 127.0.0.1:
default: SSH username: vagrant
default: SSH auth method: private key
==> default: Exporting NFS shared folders...
==> default: Preparing to edit /etc/exports. Administrator privileges 
will be required...
==> default: Mounting NFS shared folders...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mount -o vers=3 10.10.10.1:/Users/fe4c/aislegacy /vagrant
Stdout from the command:
Stderr from the command:
mount.nfs: requested NFS version or transport protocol is not supported

Here's what I think is the relevant snippet from my VagrantFile:

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
settings = YAML::load(File.read(configFile))
config.ssh.forward_agent = true
VagrantHelper.setBox(settings['provider'], config)
config.vm.hostname = settings["hostname"]
config.hostsupdater.aliases = settings["hostname-aliases"]
config.vm.network :private_network, ip: settings["ip"]
config.vm.network "forwarded_port", guest: 80, host: 8086
config.vm.network "forwarded_port", guest: 443, host: 8443
config.vm.synced_folder ".", "/vagrant", :type => "nfs", :nfs_udp => false,   
:nfs => { :mount_options => ["dmode=777","fmode=777"], :nfs_version => "3" }, 
id: settings["mount-name"]

I've tried changing the nfs_version (tried version 1-6), that didn't fix 
it. If it's a problem with the NFS version, how do I determine what version 
to use? If it's a problem with the transport protocol, how do I determine 
which value to use.

-- 
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/b1003859-d7dd-41bd-be36-0bac05bdf0f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Requested NFS version or transport protocol not supported

[Alvaro Miranda Aguilera]

try simple to complex:

config.vm.synced_folder ".", "/vagrant", :type => "nfs"


if fails, make sure you are some levels above your home

ie /users//test/another/here



On Wed, Feb 14, 2018 at 10:31 PM, Monte Gardner 
wrote:

> I have a vagrant set up that was built by someone else at my company.
> Other co-workers say it works for them on their (similarly configured)
> apple laptops. When I run vagrant up, I get the following:
>
> => default: Configuring and enabling network interfaces...
> default: SSH address: 127.0.0.1:
> default: SSH username: vagrant
> default: SSH auth method: private key
> ==> default: Exporting NFS shared folders...
> ==> default: Preparing to edit /etc/exports. Administrator privileges
> will be required...
> ==> default: Mounting NFS shared folders...
> The following SSH command responded with a non-zero exit status.
> Vagrant assumes that this means the command failed!
> mount -o vers=3 10.10.10.1:/Users/fe4c/aislegacy /vagrant
> Stdout from the command:
> Stderr from the command:
> mount.nfs: requested NFS version or transport protocol is not supported
>
> Here's what I think is the relevant snippet from my VagrantFile:
>
> Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
> settings = YAML::load(File.read(configFile))
> config.ssh.forward_agent = true
> VagrantHelper.setBox(settings['provider'], config)
> config.vm.hostname = settings["hostname"]
> config.hostsupdater.aliases = settings["hostname-aliases"]
> config.vm.network :private_network, ip: settings["ip"]
> config.vm.network "forwarded_port", guest: 80, host: 8086
> config.vm.network "forwarded_port", guest: 443, host: 8443
> config.vm.synced_folder ".", "/vagrant", :type => "nfs", :nfs_udp => false,   
> :nfs => { :mount_options => ["dmode=777","fmode=777"], :nfs_version => "3" }, 
> id: settings["mount-name"]
>
> I've tried changing the nfs_version (tried version 1-6), that didn't fix
> it. If it's a problem with the NFS version, how do I determine what version
> to use? If it's a problem with the transport protocol, how do I determine
> which value to use.
>
> --
> 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/b1003859-d7dd-41bd-be36-0bac05bdf0f1%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/CAHqq0exYWkK9N%3DM67PjMngqGNzMEW5qTN%3DVEskVeHqY_Qw53mA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Destroying a cluster

[Alvaro Miranda Aguilera]

thats a question for the people that build the project that you are using.

Alvaro.

On Wed, Feb 14, 2018 at 6:24 PM, Mahmood Naderan 
wrote:

> PS D:\dcos-vagrant> vagrant status
>  INFO dcos-vagrant: Validating Plugins...
>  INFO dcos-vagrant: Validating User Config...
>  INFO dcos-vagrant: Downloading DC/OS 1.10.4 Installer...
>  INFO dcos-vagrant: Source: https://downloads.dcos.io/
> dcos/stable/1.10.4/commit/2d45a8f9e277a60007f277f70f01d0
> 76c913a7fe/dcos_generate_config.sh
>  INFO dcos-vagrant: Destination: installers/dcos/dcos_generate_
> config-1.10.4.sh
> Progress: 0% (Rate: 471k/s, Estimated time remaining: 0:29:38))
> ^C
>
>
> So, why it does try to download a file?
> ​The same is true for global-status
> ​
>
> Regards,
> Mahmood
>
>
>
> On Wed, Feb 14, 2018 at 2:42 PM, Alvaro Miranda Aguilera <
> kiki...@gmail.com> wrote:
>
>> vagrant status
>>
>> and use those names
>>
>> or vagrant global-status and use the id
>>
>>
>> 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/CADa2P2Vck%3DtSOPxY6%3D0ZqjHsFxRyHbPRBiwOKRp3bNsmDJ
> npDA%40mail.gmail.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/CAHqq0exJCopySrOeRHqZwpofpWkHBdbBV9asGVP7jE8PA7MBFg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Using a custom version of Ansible with Vagrant

[rhys.james.campbell via Vagrant]

Hello,

Is there a way to instruct Vagrant to use a custom version of Ansible. I've 
forked the Ansible code and want to test a couple of modules without 
affecting my installed instance. 

Rhys

-- 
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/0698db80-c64c-499e-b213-605861da0da4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Virtualbox Auto Mount(shared directory) getting disabled after applying latest Security Upgrade on Windows Vagrant box

[Ritesh M]

I am using Virtual Box (5.2.6r120293) for launching Microsoft Edge 
Windows10 vagrant box.

Vagrant box Version: 2.0.1
Virtual Box (5.2.6r120293)
Host OS: Ubuntu 16.04
Guest OS: Microsoft Edge Windows 10


I have kept all the configuration & environment files in host OS(Ubuntu), 
and the vagrant box(Windows OS) access these files pointing to the shared 
folder which is automounted as '*/vagrant*'

Recently in the windows vagrant box, I got an alert to apply latest 
security path, which I went ahead and did.

After applying the patch the Auto-Mount from the Virtual box has stopped 
working.


I added below line in the Vagrantfile:

config.vm.synced_folder "/Data/vagrant22", "/vagrant", type: "virtualbox"


I also tried selecting the Auto Mount checkbox form the Virtualbox settings.


Still, the Auto Mount feature is not working.

-- 
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/f8a7cb5a-b434-449c-b80d-2180c8c03eab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.