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.
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virusvrij. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Thu, Oct 19, 2017 at 5:55 PM, Костя Хомко <[email protected]> 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 [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/vagrant-up/553aea3f-33e9-46e6-aa80-23c6a2da5c70%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/553aea3f-33e9-46e6-aa80-23c6a2da5c70%40googlegroups.com?utm_medium=email&utm_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 [email protected]. 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.
