Are you perhaps using the Windows 10 1709+ "Default Switch" NAT virtual switch? I get random network hangs if I'm using that. Have never been able to pin it down well enough to submit a case.
On Monday, April 30, 2018 at 12:48:18 AM UTC-6, [email protected] wrote: > > I have a weird issue with Windows. Our vagrant image doesn't build, but > hangs on some network activity. (the same box that is building properly on > other platforms) > > It always hangs on a `wget` instruction. It downloads a bit, and then just > hangs. Adding timeouts to the command doesn't work either. If I replace it > with a `curl` command, it will hang just a few lines further down, midway > an `apt-get update`. > > The nature in which it hangs (not responding to timeouts etc) leads me to > believe the problem is not with the script itself. > > Windows 10 pro > Vagrant 2.0.4 > Virtual Box 5.2.8 > > for reference: > - reported issue: https://github.com/Kong/kong-vagrant/issues/87 > > Any ideas? > -- 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/f002ab76-0a2a-4d49-8571-35c1ba6fc0ca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
