Vagrant really shines when it unlocks new capabilities, like running Linux 
applications from Windows! Now that Docker has supplanted Vagrant for Linux 
applications, I think Vagrant has room to grow for non-Linux guests. For 
example, BSD images cannot by run by Docker from Linux hosts. So there are gaps 
in a build bot sense that Vagrant is ideal for filling.

I’d like to use Vagrant to help setup build bots for several OS’s, so that 
C-style applications can be ported more automatedly for many kinds of users. 
However working FreeBSD, macOS / Darwin, and Windows boxes are hard to come by. 
Licensing aside, the boxes that are available are sometimes closed source (not 
even a Vagrantfile available), and other boxes fail to successfully vagrant up. 
 I think if the Vagrant community were to promote these OS’s to first tier 
support, Vagrant would find higher use in CI setups, especially for systems 
languages!

I’m looking for help getting the FreeBSD box working in macOS, for some reason 
the dang thing keeps bugging out :/

P.S., I may prefer *nix, but I am keen to support Mac and Windows users for my 
applications. Does anyone know if Apple and/or Microsoft publish or license a 
minimal development Vagrant box or some other VM format image?

-- 
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/a9409b12-e0a5-41d8-879c-5c59508d3b26%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to