[vagrant-up] ssh agent issues...
Hello, When I do "vagrant ssh" in to one of my boxes the ssh key gets added to my ssh agent. So each time I spin up a box, and ssh in to it, another key gets added. And this is a problem, because once you have a lot of keys there ssh stops becoming usefull. The problem is that when you ssh in to a machine all the keys in your agent get used in order, but most hosts are configured to refuse more than 5 loging attempts. So once I have spun up 5 boxes and logged in to them I can no longer log in to any host (except for my vagrant boxes themselves). This is annoying. What makes it even more annoying is that there isn't really a practical way of removing individua;l keys from the ssh-agent. So how do I prevent vagrant from adding a key to my ssh-agent eacht time I log in to a host? Krist -- 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/aaca6606-1caf-4ee3-a1e1-fd467ef8ac2f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[vagrant-up] Vagrant hangs when bringing up hosts in parallel.
Hello,
If I do this:
vagrant up gluster-{1..5} the boxes are brought up in parallel, and this
almost always ends up hanging somewhere, usually during provisioning of one
of the machines, or waiting for ssh
If I do:
for h in gluster-{1..5}; do vagrant up $h ; done the hosts all get booted
in sequence, and this works just fine.
But it is a bit annoying, as I can't just create a Vagrantfile containing
multiple machines, and then just do "vagrant up" to have them all start and
provisioned...,
Is there a setting to tell vagrant not to bring up hosts in the Vagrantfile
in parallel, but do them in a sequence, so I do have the comfort of a
simple command, but avoid the issues parallel execution seems to bring?
Krist
--
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/8a71b00e-0bcd-4c59-bffb-233d14832d70%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [vagrant-up] Vagrant hangs when bringing up hosts in parallel.
That helped,
But did not explain why running in parallel cause the whole vagrant up to
eventually hang somewhere...
On Thursday, 23 March 2017 10:03:54 UTC+1, Alvaro Miranda Aguilera wrote:
>
> hello
>
> did you try this?
>
>
> http://stackoverflow.com/questions/28864603/specify-no-parallel-flag-inside-vagrantfile
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
> Virusvrij.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>
> <#CAHqq0ewcBBpzDXrA6s8ZmU4TdoRmef-Q8F0u57O9yD5M6DdrnA@mail.gmail.com_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Thu, Mar 23, 2017 at 9:35 AM, Krist van Besien <krist.v...@gmail.com
> > wrote:
>
>> Hello,
>>
>> If I do this:
>>
>> vagrant up gluster-{1..5} the boxes are brought up in parallel, and this
>> almost always ends up hanging somewhere, usually during provisioning of one
>> of the machines, or waiting for ssh
>>
>> If I do:
>>
>> for h in gluster-{1..5}; do vagrant up $h ; done the hosts all get booted
>> in sequence, and this works just fine.
>>
>> But it is a bit annoying, as I can't just create a Vagrantfile containing
>> multiple machines, and then just do "vagrant up" to have them all start and
>> provisioned...,
>>
>> Is there a setting to tell vagrant not to bring up hosts in the
>> Vagrantfile in parallel, but do them in a sequence, so I do have the
>> comfort of a simple command, but avoid the issues parallel execution seems
>> to bring?
>>
>> Krist
>>
>> --
>> 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/8a71b00e-0bcd-4c59-bffb-233d14832d70%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/vagrant-up/8a71b00e-0bcd-4c59-bffb-233d14832d70%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> 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/a10d458b-1eaf-425c-94b9-5a5605d06425%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[vagrant-up] config.vm.synced_folder ignored in default Vagrantfile
Hello all,
I created my own box, and the box, and the Vagrantfile included in the box
has the following content:
Vagrant.configure("2") do |config|
config.vm.provider :libvirt do |libvirt|
libvirt.disk_bus = 'virtio'
end
config.vm.synced_folder ".", "/vagrant", disabled: true
end
However this setting is ignored. After doing a "vagrant init " I
need to edit the Vagrantfile manually to again disable the synced folder.
Why is that?
--
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/317ab26a-7323-4b15-98a7-69d97a6d11bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [vagrant-up] config.vm.synced_folder ignored in default Vagrantfile
I've been using Vagrant extensively. So I know the difference between init
and up.
My problem is the following:
- I created a box myself, by packaging an image, together with a
Vagrantfile and a Metadata.json file.
- In that Vagrantfile I have the following content:
Vagrant.configure("2") do |config|
config.vm.provider :libvirt do |libvirt|
libvirt.disk_bus = 'virtio'
end
config.vm.synced_folder ".", "/vagrant", disabled: true
end
So I tarred/ziped those three files in to a new box, and imported that in
to Vagrant.
Then I tested this. I created a new directory, and in that directory I did:
vagrant init newbox
vagrant up
What I expected to happen:
The box is started, but no synced folder is setup.
What I got:
Box is started, and vagrant attempts to setup a synced folder, which fails
on this particular image. (and this is why I want it to be disabled by
default)
In other words, I expect (and the documentation has led me to expect this)
that the config you put in the Vagrantfile you package in a box is
interpreted as a default for that box, and that this config is merged with
the Vagrantfile created by vagrant init in your working directory. In other
words, I expect to be able to set defaults in a box.
Are my expectations incorrect? Or did I do something wrong? Or is this a
bug?
On Friday, 7 July 2017 17:47:38 UTC+1, Salty Vagrant wrote:
>
> I suspect this is simply a misunderstanding of the vagrant commands.
>
> Once you have your edited Vagrantfile (with the synced_folder disabled)
> you should use ‘vagrant up’ NOT ‘vagrant init’.
>
> ‘vagrant init’ creates a new Vagrantfile and sets the vm/box to the value
> you provide on the command line (this will overwrite the one you previously
> created).
>
> ‘vagrant up’ on the other hand will start the VM specified by the
> Vagrantfile.
>
> On 7 Jul 2017, at 16:44, Krist van Besien wrote:
>
> Hello all,
>
> I created my own box, and the box, and the Vagrantfile included in the box
> has the following content:
>
> Vagrant.configure("2") do |config|
> config.vm.provider :libvirt do |libvirt|
> libvirt.disk_bus = 'virtio'
> end
> config.vm.synced_folder ".", "/vagrant", disabled: true
> end
>
>
> However this setting is ignored. After doing a "vagrant init " I
> need to edit the Vagrantfile manually to again disable the synced folder.
>
> Why is that?
>
>
>
>
>
>
> --
> 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/317ab26a-7323-4b15-98a7-69d97a6d11bd%40googlegroups.com
>
> <https://groups.google.com/d/msgid/vagrant-up/317ab26a-7323-4b15-98a7-69d97a6d11bd%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
--
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/5345e486-c18f-4d34-93a3-62b03e557dad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
