network issue with creating docker-machine on Vagrant

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

network issue with creating docker-machine on Vagrant

Костя Хомко
Hello guys. 

I am trying to solve an issue with provisioning docker-machine on Vagrant using virtualbox provider about a month but still have no any progress.

The issue is docker-machine can not be created properly and can not start (ssh issue, waiting for ip and so on) on Vagrant box Centos 7.3.

What i have tried to do:

1. Used nested virtualisation: Virtualbox for Vagrant and Virtualbox for docker-machine. BUT, as google tells that Virtualbox does not support nested virtualisation so this binding Host VirtualBox -> guest VirtualBox does not work.

2. That is why i have tried later to ise KVM as host hypervisor. Enabled nested virtualisation in configuration files. But still no luck. Faced with the same issue. "Waiting for IP during call of SSH".

3. I even tried add vagrant user to sudoers with NOPASSWD parameter (in case if ssh fails do to attempt of login), but error still has a place.

4. Tried create docker-machine with "native-ssh" parameter. No luck.

5. Tried to turn of firewall on vagrant and host os, but in this case connectivity does not work at all. 

6. Tried to set selinux in permissive mode but it also does not help.

7. Tried to change virtualbox NIC from intel to VIRTIO type. But is has no affect. Error still the same.

8. Also tried to use for docker-machine creation generic driver instead of virtualbox driver but i am facing with the same issue.

So, looks like after all of this that error is not in virtualbox and not in docker, but in vagrant. And i am little bit tired of this and have no more ideas where to find.
 
Please help to find a root cause and fix it.

Thanks.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/553aea3f-33e9-46e6-aa80-23c6a2da5c70%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: network issue with creating docker-machine on Vagrant

Alvaro Miranda Aguilera
why you want to use that nested setup?

you can have Vagrant installed into a linux VM and create docker containers, no need to do nested setup.

Virusvrij. www.avast.com

On Thu, Oct 19, 2017 at 5:55 PM, Костя Хомко <[hidden email]> wrote:
Hello guys. 

I am trying to solve an issue with provisioning docker-machine on Vagrant using virtualbox provider about a month but still have no any progress.

The issue is docker-machine can not be created properly and can not start (ssh issue, waiting for ip and so on) on Vagrant box Centos 7.3.

What i have tried to do:

1. Used nested virtualisation: Virtualbox for Vagrant and Virtualbox for docker-machine. BUT, as google tells that Virtualbox does not support nested virtualisation so this binding Host VirtualBox -> guest VirtualBox does not work.

2. That is why i have tried later to ise KVM as host hypervisor. Enabled nested virtualisation in configuration files. But still no luck. Faced with the same issue. "Waiting for IP during call of SSH".

3. I even tried add vagrant user to sudoers with NOPASSWD parameter (in case if ssh fails do to attempt of login), but error still has a place.

4. Tried create docker-machine with "native-ssh" parameter. No luck.

5. Tried to turn of firewall on vagrant and host os, but in this case connectivity does not work at all. 

6. Tried to set selinux in permissive mode but it also does not help.

7. Tried to change virtualbox NIC from intel to VIRTIO type. But is has no affect. Error still the same.

8. Also tried to use for docker-machine creation generic driver instead of virtualbox driver but i am facing with the same issue.

So, looks like after all of this that error is not in virtualbox and not in docker, but in vagrant. And i am little bit tired of this and have no more ideas where to find.
 
Please help to find a root cause and fix it.

Thanks.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/553aea3f-33e9-46e6-aa80-23c6a2da5c70%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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0exSaZ01u_9i2hgeK%3Dmq7fFq%2Brzaf2eWv0FAgsQ9t8jz6w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: network issue with creating docker-machine on Vagrant

Костя Хомко
Hello. 
I need nested virtualisation for docker swarm. Not sure that it is enough only Vagrantfile for this.

пятница, 20 октября 2017 г., 9:48:57 UTC+3 пользователь Alvaro Miranda Aguilera написал:
why you want to use that nested setup?

you can have Vagrant installed into a linux VM and create docker containers, no need to do nested setup.

<a href="https://www.avast.com/sig-email?utm_medium=email&amp;utm_source=link&amp;utm_campaign=sig-email&amp;utm_content=webmail" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.avast.com%2Fsig-email%3Futm_medium%3Demail%26utm_source%3Dlink%26utm_campaign%3Dsig-email%26utm_content%3Dwebmail\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFuftbSgu95389HmI-4V1nVL3tGJw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.avast.com%2Fsig-email%3Futm_medium%3Demail%26utm_source%3Dlink%26utm_campaign%3Dsig-email%26utm_content%3Dwebmail\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFuftbSgu95389HmI-4V1nVL3tGJw&#39;;return true;"> Virusvrij. <a href="https://www.avast.com/sig-email?utm_medium=email&amp;utm_source=link&amp;utm_campaign=sig-email&amp;utm_content=webmail" style="color:#4453ea" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.avast.com%2Fsig-email%3Futm_medium%3Demail%26utm_source%3Dlink%26utm_campaign%3Dsig-email%26utm_content%3Dwebmail\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFuftbSgu95389HmI-4V1nVL3tGJw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.avast.com%2Fsig-email%3Futm_medium%3Demail%26utm_source%3Dlink%26utm_campaign%3Dsig-email%26utm_content%3Dwebmail\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFuftbSgu95389HmI-4V1nVL3tGJw&#39;;return true;">www.avast.com
<a href="#CAHqq0exSaZ01u_9i2hgeK=mq7fFq+rzaf2eWv0FAgsQ9t8jz6w@mail.gmail.com_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1" rel="nofollow" onmousedown="this.href=&#39;#CAHqq0exSaZ01u_9i2hgeK\x3dmq7fFq+rzaf2eWv0FAgsQ9t8jz6w@mail.gmail.com_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2&#39;;return true;" onclick="this.href=&#39;#CAHqq0exSaZ01u_9i2hgeK\x3dmq7fFq+rzaf2eWv0FAgsQ9t8jz6w@mail.gmail.com_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2&#39;;return true;">

On Thu, Oct 19, 2017 at 5:55 PM, Костя Хомко <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="72FjNV9gBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">kosty...@...> wrote:
Hello guys. 

I am trying to solve an issue with provisioning docker-machine on Vagrant using virtualbox provider about a month but still have no any progress.

The issue is docker-machine can not be created properly and can not start (ssh issue, waiting for ip and so on) on Vagrant box Centos 7.3.

What i have tried to do:

1. Used nested virtualisation: Virtualbox for Vagrant and Virtualbox for docker-machine. BUT, as google tells that Virtualbox does not support nested virtualisation so this binding Host VirtualBox -> guest VirtualBox does not work.

2. That is why i have tried later to ise KVM as host hypervisor. Enabled nested virtualisation in configuration files. But still no luck. Faced with the same issue. "Waiting for IP during call of SSH".

3. I even tried add vagrant user to sudoers with NOPASSWD parameter (in case if ssh fails do to attempt of login), but error still has a place.

4. Tried create docker-machine with "native-ssh" parameter. No luck.

5. Tried to turn of firewall on vagrant and host os, but in this case connectivity does not work at all. 

6. Tried to set selinux in permissive mode but it also does not help.

7. Tried to change virtualbox NIC from intel to VIRTIO type. But is has no affect. Error still the same.

8. Also tried to use for docker-machine creation generic driver instead of virtualbox driver but i am facing with the same issue.

So, looks like after all of this that error is not in virtualbox and not in docker, but in vagrant. And i am little bit tired of this and have no more ideas where to find.
 
Please help to find a root cause and fix it.

Thanks.

--
This mailing list is governed under the HashiCorp Community Guidelines - <a href="https://www.hashicorp.com/community-guidelines.html" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.hashicorp.com%2Fcommunity-guidelines.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGHa_CaKfZaJiwbkUndUQbVGlQCDw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.hashicorp.com%2Fcommunity-guidelines.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGHa_CaKfZaJiwbkUndUQbVGlQCDw&#39;;return true;">https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: <a href="https://github.com/mitchellh/vagrant/issues" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHxcA5DuHlQlPInMi_k1Pz4pMNqNw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHxcA5DuHlQlPInMi_k1Pz4pMNqNw&#39;;return true;">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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="72FjNV9gBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">vagrant-up+...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/vagrant-up/553aea3f-33e9-46e6-aa80-23c6a2da5c70%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/vagrant-up/553aea3f-33e9-46e6-aa80-23c6a2da5c70%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/vagrant-up/553aea3f-33e9-46e6-aa80-23c6a2da5c70%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/vagrant-up/553aea3f-33e9-46e6-aa80-23c6a2da5c70%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/fae51ddd-cb0f-495b-8702-5657a7de79ff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: network issue with creating docker-machine on Vagrant

Alvaro Miranda Aguilera
I am not sure Vagrant is the right tool for you if you want docker swarm.


On Fri, Oct 20, 2017 at 10:29 AM, Костя Хомко <[hidden email]> wrote:
Hello. 
I need nested virtualisation for docker swarm. Not sure that it is enough only Vagrantfile for this.

пятница, 20 октября 2017 г., 9:48:57 UTC+3 пользователь Alvaro Miranda Aguilera написал:
why you want to use that nested setup?

you can have Vagrant installed into a linux VM and create docker containers, no need to do nested setup.

Virusvrij. www.avast.com

On Thu, Oct 19, 2017 at 5:55 PM, Костя Хомко <[hidden email]> wrote:
Hello guys. 

I am trying to solve an issue with provisioning docker-machine on Vagrant using virtualbox provider about a month but still have no any progress.

The issue is docker-machine can not be created properly and can not start (ssh issue, waiting for ip and so on) on Vagrant box Centos 7.3.

What i have tried to do:

1. Used nested virtualisation: Virtualbox for Vagrant and Virtualbox for docker-machine. BUT, as google tells that Virtualbox does not support nested virtualisation so this binding Host VirtualBox -> guest VirtualBox does not work.

2. That is why i have tried later to ise KVM as host hypervisor. Enabled nested virtualisation in configuration files. But still no luck. Faced with the same issue. "Waiting for IP during call of SSH".

3. I even tried add vagrant user to sudoers with NOPASSWD parameter (in case if ssh fails do to attempt of login), but error still has a place.

4. Tried create docker-machine with "native-ssh" parameter. No luck.

5. Tried to turn of firewall on vagrant and host os, but in this case connectivity does not work at all. 

6. Tried to set selinux in permissive mode but it also does not help.

7. Tried to change virtualbox NIC from intel to VIRTIO type. But is has no affect. Error still the same.

8. Also tried to use for docker-machine creation generic driver instead of virtualbox driver but i am facing with the same issue.

So, looks like after all of this that error is not in virtualbox and not in docker, but in vagrant. And i am little bit tired of this and have no more ideas where to find.
 
Please help to find a root cause and fix it.

Thanks.

--
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/553aea3f-33e9-46e6-aa80-23c6a2da5c70%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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/fae51ddd-cb0f-495b-8702-5657a7de79ff%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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyg%2BFJ-iBUwX2Xb_rVsZwVVDnWi6CrTT0BXAxCX4SZ%3DSg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: network issue with creating docker-machine on Vagrant

Костя Хомко
May be you are right but it is not my wish, it is a test task of employer to be able to show your skills before it can make you job offer.
It is almost done, actually, but only fails on final step when i am trying create docker-machine in Vagrant environment.
I have searched many sites but still have no one proper working solution how to do it. Many people write about "virtio" provider\driver in order to make it work but it has relation to docker, kvm, virtualbox as of off them have such option of paravirtprovider. So it is not still clear where exactly it has to be applied.

пятница, 20 октября 2017 г., 11:31:49 UTC+3 пользователь Alvaro Miranda Aguilera написал:
I am not sure Vagrant is the right tool for you if you want docker swarm.


On Fri, Oct 20, 2017 at 10:29 AM, Костя Хомко <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="mnAGOvxlBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">kosty...@...> wrote:
Hello. 
I need nested virtualisation for docker swarm. Not sure that it is enough only Vagrantfile for this.

пятница, 20 октября 2017 г., 9:48:57 UTC+3 пользователь Alvaro Miranda Aguilera написал:
why you want to use that nested setup?

you can have Vagrant installed into a linux VM and create docker containers, no need to do nested setup.

<a href="https://www.avast.com/sig-email?utm_medium=email&amp;utm_source=link&amp;utm_campaign=sig-email&amp;utm_content=webmail" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.avast.com%2Fsig-email%3Futm_medium%3Demail%26utm_source%3Dlink%26utm_campaign%3Dsig-email%26utm_content%3Dwebmail\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFuftbSgu95389HmI-4V1nVL3tGJw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.avast.com%2Fsig-email%3Futm_medium%3Demail%26utm_source%3Dlink%26utm_campaign%3Dsig-email%26utm_content%3Dwebmail\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFuftbSgu95389HmI-4V1nVL3tGJw&#39;;return true;"> Virusvrij. <a href="https://www.avast.com/sig-email?utm_medium=email&amp;utm_source=link&amp;utm_campaign=sig-email&amp;utm_content=webmail" style="color:#4453ea" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.avast.com%2Fsig-email%3Futm_medium%3Demail%26utm_source%3Dlink%26utm_campaign%3Dsig-email%26utm_content%3Dwebmail\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFuftbSgu95389HmI-4V1nVL3tGJw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.avast.com%2Fsig-email%3Futm_medium%3Demail%26utm_source%3Dlink%26utm_campaign%3Dsig-email%26utm_content%3Dwebmail\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFuftbSgu95389HmI-4V1nVL3tGJw&#39;;return true;">www.avast.com
<a href="#CAHqq0eyg+FJ-iBUwX2Xb_rVsZwVVDnWi6CrTT0BXAxCX4SZ=Sg@mail.gmail.com_m_-5107488277616300050_CAHqq0exSaZ01u_9i2hgeK=mq7fFq+rzaf2eWv0FAgsQ9t8jz6w@mail.gmail.com_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1" rel="nofollow" onmousedown="this.href=&#39;#CAHqq0eyg+FJ-iBUwX2Xb_rVsZwVVDnWi6CrTT0BXAxCX4SZ\x3dSg@mail.gmail.com_m_-5107488277616300050_CAHqq0exSaZ01u_9i2hgeK\x3dmq7fFq+rzaf2eWv0FAgsQ9t8jz6w@mail.gmail.com_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2&#39;;return true;" onclick="this.href=&#39;#CAHqq0eyg+FJ-iBUwX2Xb_rVsZwVVDnWi6CrTT0BXAxCX4SZ\x3dSg@mail.gmail.com_m_-5107488277616300050_CAHqq0exSaZ01u_9i2hgeK\x3dmq7fFq+rzaf2eWv0FAgsQ9t8jz6w@mail.gmail.com_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2&#39;;return true;">

On Thu, Oct 19, 2017 at 5:55 PM, Костя Хомко <[hidden email]> wrote:
Hello guys. 

I am trying to solve an issue with provisioning docker-machine on Vagrant using virtualbox provider about a month but still have no any progress.

The issue is docker-machine can not be created properly and can not start (ssh issue, waiting for ip and so on) on Vagrant box Centos 7.3.

What i have tried to do:

1. Used nested virtualisation: Virtualbox for Vagrant and Virtualbox for docker-machine. BUT, as google tells that Virtualbox does not support nested virtualisation so this binding Host VirtualBox -> guest VirtualBox does not work.

2. That is why i have tried later to ise KVM as host hypervisor. Enabled nested virtualisation in configuration files. But still no luck. Faced with the same issue. "Waiting for IP during call of SSH".

3. I even tried add vagrant user to sudoers with NOPASSWD parameter (in case if ssh fails do to attempt of login), but error still has a place.

4. Tried create docker-machine with "native-ssh" parameter. No luck.

5. Tried to turn of firewall on vagrant and host os, but in this case connectivity does not work at all. 

6. Tried to set selinux in permissive mode but it also does not help.

7. Tried to change virtualbox NIC from intel to VIRTIO type. But is has no affect. Error still the same.

8. Also tried to use for docker-machine creation generic driver instead of virtualbox driver but i am facing with the same issue.

So, looks like after all of this that error is not in virtualbox and not in docker, but in vagrant. And i am little bit tired of this and have no more ideas where to find.
 
Please help to find a root cause and fix it.

Thanks.

--
This mailing list is governed under the HashiCorp Community Guidelines - <a href="https://www.hashicorp.com/community-guidelines.html" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.hashicorp.com%2Fcommunity-guidelines.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGHa_CaKfZaJiwbkUndUQbVGlQCDw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.hashicorp.com%2Fcommunity-guidelines.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGHa_CaKfZaJiwbkUndUQbVGlQCDw&#39;;return true;">https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: <a href="https://github.com/mitchellh/vagrant/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHxcA5DuHlQlPInMi_k1Pz4pMNqNw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHxcA5DuHlQlPInMi_k1Pz4pMNqNw&#39;;return true;">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 <a href="https://groups.google.com/d/msgid/vagrant-up/553aea3f-33e9-46e6-aa80-23c6a2da5c70%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/vagrant-up/553aea3f-33e9-46e6-aa80-23c6a2da5c70%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/vagrant-up/553aea3f-33e9-46e6-aa80-23c6a2da5c70%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/vagrant-up/553aea3f-33e9-46e6-aa80-23c6a2da5c70%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.



--
Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - <a href="https://www.hashicorp.com/community-guidelines.html" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.hashicorp.com%2Fcommunity-guidelines.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGHa_CaKfZaJiwbkUndUQbVGlQCDw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.hashicorp.com%2Fcommunity-guidelines.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGHa_CaKfZaJiwbkUndUQbVGlQCDw&#39;;return true;">https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: <a href="https://github.com/mitchellh/vagrant/issues" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHxcA5DuHlQlPInMi_k1Pz4pMNqNw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHxcA5DuHlQlPInMi_k1Pz4pMNqNw&#39;;return true;">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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="mnAGOvxlBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">vagrant-up+...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/vagrant-up/fae51ddd-cb0f-495b-8702-5657a7de79ff%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/vagrant-up/fae51ddd-cb0f-495b-8702-5657a7de79ff%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/vagrant-up/fae51ddd-cb0f-495b-8702-5657a7de79ff%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/vagrant-up/fae51ddd-cb0f-495b-8702-5657a7de79ff%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/21c0c12b-9673-41b1-be0e-9c9403d55f64%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: network issue with creating docker-machine on Vagrant

Alvaro Miranda Aguilera
Hello

Not sure if I follow correctly

perhaps you got mixed between docker-engine and docker-swarm ? docker-machine? etc

you can have multiple docker hosts to use docker swarm

ir



--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezThjagMCGRA8VpoWXa-ZnZKQrS%3Dkrhj4JV%3DoQLJykt%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: network issue with creating docker-machine on Vagrant

Костя Хомко
No. I have not mixed. I initially created a docker swarm with the command "docker swarm init" and then i was going to add two more nodes which should be created using "docker-machine create ...."  following this manual: https://docs.docker.com/get-started/part4/#create-a-cluster
But anyway thanks for your reference. I will try to use this Vagrantfile as workaround if i will not manage to find the root cause why it fails in current state when i am trying to do it not with help of Vagrantfile shell provisioning but just using Ansible playbook with shell commands "vagrant ssh -c "docker-machine create --driver Virtualbox VM".

пятница, 20 октября 2017 г., 19:20:40 UTC+3 пользователь Alvaro Miranda Aguilera написал:
Hello

Not sure if I follow correctly

perhaps you got mixed between docker-engine and docker-swarm ? docker-machine? etc

you can have multiple docker hosts to use docker swarm

ir

<a href="https://github.com/tdi/vagrant-docker-swarm/blob/master/Vagrantfile" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Ftdi%2Fvagrant-docker-swarm%2Fblob%2Fmaster%2FVagrantfile\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE1XlTfxG4xmtoV71bModSGtU3auw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Ftdi%2Fvagrant-docker-swarm%2Fblob%2Fmaster%2FVagrantfile\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE1XlTfxG4xmtoV71bModSGtU3auw&#39;;return true;">https://github.com/tdi/vagrant-docker-swarm/blob/master/Vagrantfile


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/50088d83-ba03-4586-b23b-44c75501f4d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: network issue with creating docker-machine on Vagrant

Joaquin Menchaca
In reply to this post by Alvaro Miranda Aguilera
I don't think you need to do nested for Docker Swarm unless you are specifically using Docker Swarm 1.x.  Swarm is integrated into current docker, so there is no need.  There's a lot of instructions and books out there that document the older docker-machine method.

Docker-Machine is going to be hard to get working, as you have to do a virtual system inside a virtual system.  There has been some work to get this to work, but I am not sure how well it works.


On Friday, October 20, 2017 at 1:31:49 AM UTC-7, Alvaro Miranda Aguilera wrote:
I am not sure Vagrant is the right tool for you if you want docker swarm.


On Fri, Oct 20, 2017 at 10:29 AM, Костя Хомко <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="mnAGOvxlBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">kosty...@...> wrote:
Hello. 
I need nested virtualisation for docker swarm. Not sure that it is enough only Vagrantfile for this.

пятница, 20 октября 2017 г., 9:48:57 UTC+3 пользователь Alvaro Miranda Aguilera написал:
why you want to use that nested setup?

you can have Vagrant installed into a linux VM and create docker containers, no need to do nested setup.

<a href="https://www.avast.com/sig-email?utm_medium=email&amp;utm_source=link&amp;utm_campaign=sig-email&amp;utm_content=webmail" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.avast.com%2Fsig-email%3Futm_medium%3Demail%26utm_source%3Dlink%26utm_campaign%3Dsig-email%26utm_content%3Dwebmail\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFuftbSgu95389HmI-4V1nVL3tGJw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.avast.com%2Fsig-email%3Futm_medium%3Demail%26utm_source%3Dlink%26utm_campaign%3Dsig-email%26utm_content%3Dwebmail\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFuftbSgu95389HmI-4V1nVL3tGJw&#39;;return true;"> Virusvrij. <a href="https://www.avast.com/sig-email?utm_medium=email&amp;utm_source=link&amp;utm_campaign=sig-email&amp;utm_content=webmail" style="color:#4453ea" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.avast.com%2Fsig-email%3Futm_medium%3Demail%26utm_source%3Dlink%26utm_campaign%3Dsig-email%26utm_content%3Dwebmail\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFuftbSgu95389HmI-4V1nVL3tGJw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.avast.com%2Fsig-email%3Futm_medium%3Demail%26utm_source%3Dlink%26utm_campaign%3Dsig-email%26utm_content%3Dwebmail\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFuftbSgu95389HmI-4V1nVL3tGJw&#39;;return true;">www.avast.com
<a href="#CAHqq0eyg+FJ-iBUwX2Xb_rVsZwVVDnWi6CrTT0BXAxCX4SZ=Sg@mail.gmail.com_m_-5107488277616300050_CAHqq0exSaZ01u_9i2hgeK=mq7fFq+rzaf2eWv0FAgsQ9t8jz6w@mail.gmail.com_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1" rel="nofollow" onmousedown="this.href=&#39;#CAHqq0eyg+FJ-iBUwX2Xb_rVsZwVVDnWi6CrTT0BXAxCX4SZ\x3dSg@mail.gmail.com_m_-5107488277616300050_CAHqq0exSaZ01u_9i2hgeK\x3dmq7fFq+rzaf2eWv0FAgsQ9t8jz6w@mail.gmail.com_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2&#39;;return true;" onclick="this.href=&#39;#CAHqq0eyg+FJ-iBUwX2Xb_rVsZwVVDnWi6CrTT0BXAxCX4SZ\x3dSg@mail.gmail.com_m_-5107488277616300050_CAHqq0exSaZ01u_9i2hgeK\x3dmq7fFq+rzaf2eWv0FAgsQ9t8jz6w@mail.gmail.com_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2&#39;;return true;">

On Thu, Oct 19, 2017 at 5:55 PM, Костя Хомко <[hidden email]> wrote:
Hello guys. 

I am trying to solve an issue with provisioning docker-machine on Vagrant using virtualbox provider about a month but still have no any progress.

The issue is docker-machine can not be created properly and can not start (ssh issue, waiting for ip and so on) on Vagrant box Centos 7.3.

What i have tried to do:

1. Used nested virtualisation: Virtualbox for Vagrant and Virtualbox for docker-machine. BUT, as google tells that Virtualbox does not support nested virtualisation so this binding Host VirtualBox -> guest VirtualBox does not work.

2. That is why i have tried later to ise KVM as host hypervisor. Enabled nested virtualisation in configuration files. But still no luck. Faced with the same issue. "Waiting for IP during call of SSH".

3. I even tried add vagrant user to sudoers with NOPASSWD parameter (in case if ssh fails do to attempt of login), but error still has a place.

4. Tried create docker-machine with "native-ssh" parameter. No luck.

5. Tried to turn of firewall on vagrant and host os, but in this case connectivity does not work at all. 

6. Tried to set selinux in permissive mode but it also does not help.

7. Tried to change virtualbox NIC from intel to VIRTIO type. But is has no affect. Error still the same.

8. Also tried to use for docker-machine creation generic driver instead of virtualbox driver but i am facing with the same issue.

So, looks like after all of this that error is not in virtualbox and not in docker, but in vagrant. And i am little bit tired of this and have no more ideas where to find.
 
Please help to find a root cause and fix it.

Thanks.

--
This mailing list is governed under the HashiCorp Community Guidelines - <a href="https://www.hashicorp.com/community-guidelines.html" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.hashicorp.com%2Fcommunity-guidelines.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGHa_CaKfZaJiwbkUndUQbVGlQCDw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.hashicorp.com%2Fcommunity-guidelines.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGHa_CaKfZaJiwbkUndUQbVGlQCDw&#39;;return true;">https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: <a href="https://github.com/mitchellh/vagrant/issues" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHxcA5DuHlQlPInMi_k1Pz4pMNqNw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHxcA5DuHlQlPInMi_k1Pz4pMNqNw&#39;;return true;">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 <a href="https://groups.google.com/d/msgid/vagrant-up/553aea3f-33e9-46e6-aa80-23c6a2da5c70%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/vagrant-up/553aea3f-33e9-46e6-aa80-23c6a2da5c70%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/vagrant-up/553aea3f-33e9-46e6-aa80-23c6a2da5c70%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/vagrant-up/553aea3f-33e9-46e6-aa80-23c6a2da5c70%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.



--
Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - <a href="https://www.hashicorp.com/community-guidelines.html" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.hashicorp.com%2Fcommunity-guidelines.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGHa_CaKfZaJiwbkUndUQbVGlQCDw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.hashicorp.com%2Fcommunity-guidelines.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGHa_CaKfZaJiwbkUndUQbVGlQCDw&#39;;return true;">https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: <a href="https://github.com/mitchellh/vagrant/issues" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHxcA5DuHlQlPInMi_k1Pz4pMNqNw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHxcA5DuHlQlPInMi_k1Pz4pMNqNw&#39;;return true;">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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="mnAGOvxlBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">vagrant-up+...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/vagrant-up/fae51ddd-cb0f-495b-8702-5657a7de79ff%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/vagrant-up/fae51ddd-cb0f-495b-8702-5657a7de79ff%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/vagrant-up/fae51ddd-cb0f-495b-8702-5657a7de79ff%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/vagrant-up/fae51ddd-cb0f-495b-8702-5657a7de79ff%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/bbc0f447-d6c1-45a7-81d5-4c7e99748ee8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.